From: Johannes Berg <johannes@sipsolutions.net>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Intel Linux Wireless <linuxwifi@intel.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [linux-next] iwl_mvm_get_key_sta_id() suspicious RCU usage
Date: Fri, 11 Dec 2015 14:49:01 +0100 [thread overview]
Message-ID: <1449841741.2324.2.camel@sipsolutions.net> (raw)
In-Reply-To: <20151211134418.GA29351@swordfish> (sfid-20151211_144614_821713_0C346E06)
On Fri, 2015-12-11 at 22:44 +0900, Sergey Senozhatsky wrote:
> [ 6385.246300] drivers/net/wireless/intel/iwlwifi/mvm/sta.c:1226
> suspicious rcu_dereference_protected() usage!
>
Funny, Laura Abbott also reported this bug earlier today :)
I've sent out a fix, you can see it here:
https://patchwork.ozlabs.org/patch/555587/
johannes
next prev parent reply other threads:[~2015-12-11 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 13:44 [linux-next] iwl_mvm_get_key_sta_id() suspicious RCU usage Sergey Senozhatsky
2015-12-11 13:49 ` Johannes Berg [this message]
2015-12-12 0:05 ` Sergey Senozhatsky
2015-12-12 0:11 ` Sergey Senozhatsky
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=1449841741.2324.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sergey.senozhatsky@gmail.com \
/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).