[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1380131303.2222.9.camel@bwh-desktop.uk.level5networks.com>
Date: Wed, 25 Sep 2013 18:48:23 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
CC: <linux-kernel@...r.kernel.org>, <mingo@...nel.org>,
<laijs@...fujitsu.com>, <dipankar@...ibm.com>,
<akpm@...ux-foundation.org>, <mathieu.desnoyers@...icios.com>,
<josh@...htriplett.org>, <niv@...ibm.com>, <tglx@...utronix.de>,
<peterz@...radead.org>, <rostedt@...dmis.org>,
<dhowells@...hat.com>, <edumazet@...gle.com>, <darren@...art.com>,
<fweisbec@...il.com>, <sbw@....edu>,
Stephen Hemminger <stephen@...workplumber.org>,
"David S. Miller" <davem@...emloft.net>,
<bridge@...ts.linux-foundation.org>, <netdev@...r.kernel.org>
Subject: Re: [PATCH tip/core/rcu 04/13] wireless: Apply rcu_access_pointer()
to avoid sparse false positive
On Tue, 2013-09-24 at 18:35 -0700, Paul E. McKenney wrote:
> From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
>
> The sparse checking for rcu_assign_pointer() was recently upgraded
> to reject non-__kernel address spaces. This also rejects __rcu,
> which is almost always the right thing to do. However, the uses in
> cfg80211_combine_bsses() and cfg80211_bss_update() are legitimate:
> They is assigning a pointer to an element from an RCU-protected list,
[...]
'They is'? This error is also in the commit messsages for the bridge
and mac80211 patches, and maybe others that weren't sent to netdev.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
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/
Powered by blists - more mailing lists