linux-kernel - Re: [PATCH] rcu: remove SPARSE_RCU

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]

Date:	Tue, 4 Jan 2011 11:36:02 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Lai Jiangshan <laijs@...fujitsu.com>
Cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] rcu: remove SPARSE_RCU_POINTER

On Tuesday 04 January 2011 09:43:01 Lai Jiangshan wrote:
> As I known, __rcu annotations do not effect the result compiled kernel.
> 
> They work only when we use spare("make C=1" or "make C=2"),
> So we don't need another new switch for it since we have one
> for debugging(use spare or not).
> 
> signed-off-by: Lai Jiangshan <laijs@...fujitsu.com>

The intention of this option was to avoid introducing an excessive
number of false positives when using sparse.

We should only make that unconditional if we are reasonably convinced
that all the majority of warnings caused by it should actually
lead to changes in the code.

	Arnd
--
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/