From: Valdis.Kletnieks@vt.edu
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
"John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: 2.6.34-rc5-mmotm0428 - 2 RCU whinges in mac80211
Date: Thu, 06 May 2010 14:29:44 -0400 [thread overview]
Message-ID: <8269.1273170584@localhost> (raw)
In-Reply-To: Your message of "Thu, 06 May 2010 19:58:16 +0200." <1273168696.23199.0.camel@jlt3.sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
On Thu, 06 May 2010 19:58:16 +0200, Johannes Berg said:
> On Thu, 2010-05-06 at 13:35 -0400, Valdis.Kletnieks@vt.edu wrote:
> > Spotted these in my dmesg, hopefully somebody is interested...
> >
> > [ 54.076863] wlan0: deauthenticating from 00:11:20:a4:4c:11 by local choice (reason=3)
> > [ 54.080580]
> > [ 54.080581] ===================================================
> > [ 54.080584] [ INFO: suspicious rcu_dereference_check() usage. ]
> > [ 54.080586] ---------------------------------------------------
> > [ 54.080589] net/mac80211/sta_info.c:858 invoked rcu_dereference_check() without protection!
>
> I'm pretty sure I fixed those so there should be a patch on its way to
> or in mainline somewhere.
Oh, OK. I didn't remember seeing them mentioned before, but I must have
missed somebody else's post about it due to the lkml firehose effect. I've
moved these to my "whinge if it isn't fixed in the next -mmotm" queue.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2010-05-06 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 17:35 2.6.34-rc5-mmotm0428 - 2 RCU whinges in mac80211 Valdis.Kletnieks-PjAqaU27lzQ
2010-05-06 17:58 ` Johannes Berg
2010-05-06 18:29 ` Valdis.Kletnieks [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8269.1273170584@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).