LKML Archive on
help / color / mirror / Atom feed
From: Brice Goglin <>
To: "Paul E. McKenney" <>
Cc: LKML <>
Subject: sparse errors in srcu.h
Date: Wed, 06 Dec 2006 10:50:14 +0100	[thread overview]
Message-ID: <> (raw)


When running sparse checks on a file that ends up including srcu.h, we
get the following warnings:

    include/linux/srcu.h:52:44: error: undefined identifier 'sp'
    include/linux/srcu.h:52:44: error: bad constant expression
    include/linux/srcu.h:53:56: error: undefined identifier 'sp'
    include/linux/srcu.h:53:56: error: bad constant expression

It seems to be caused by the following lines:

    int srcu_read_lock(struct srcu_struct *sp) __acquires(sp);
    void srcu_read_unlock(struct srcu_struct *sp, int idx) __releases(sp);

which come from the following commit.

    commit 621934ee7ed5b073c7fd638b347e632c53572761
    Author: Paul E. McKenney <>
    Date:   Wed Oct 4 02:17:02 2006 -0700

    [PATCH] srcu-3: RCU variant permitting read-side blocking

I was wondering if there is a way to fix those errors...


             reply	other threads:[~2006-12-06  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06  9:50 Brice Goglin [this message]
2006-12-06 16:15 ` Paul E. McKenney
2006-12-07  9:26   ` Brice Goglin
2006-12-07  9:32   ` Brice Goglin
2006-12-07  9:34   ` Brice Goglin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: sparse errors in srcu.h' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).