linux-kernel - Re: sparse errors in srcu.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061206161537.GA2013@linux.vnet.ibm.com>
Date:	Wed, 6 Dec 2006 08:15:37 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Brice Goglin <Brice.Goglin@...-lyon.org>
Cc:	"Paul E. McKenney" <paulmck@...ibm.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: sparse errors in srcu.h

On Wed, Dec 06, 2006 at 10:50:14AM +0100, Brice Goglin wrote:
> Hi,
> 
> 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 <paulmck@...ibm.com>
>     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...

I believe that you need to update your version of sparse to 0.1.
See http://lwn.net/Articles/208312/ for more info.

							Thanx, Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/