From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: David Spinadel <dvdspndl@gmail.com>,
linux-wireless@vger.kernel.org, hostap@lists.shmoo.com
Subject: Re: rcutree tree warning during P2P device support testing
Date: Wed, 20 Mar 2013 22:29:07 +0100 [thread overview]
Message-ID: <1363814947.9284.10.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <514A274F.5030303@broadcom.com>
On Wed, 2013-03-20 at 22:17 +0100, Arend van Spriel wrote:
> > Hmm, why would stopping the supplicant cause brcmfmac to unload?? Or are
> > you saying you first stop the supplicant, which gets you that warning,
> > and then unload fails?
>
> Indeed, upon stopping wpa_supplicant I get the warning. And doing a
> rmmod from the command line after that fails in the hang.
Right, ok.
> >> [ 1634.039095] WARNING: at kernel/rcutree.c:1960
> >> rcu_process_callbacks+0x469/0x560()
> >
> >> [ 1634.133917] Call Trace:
> >> [ 1634.139833] [<c1039c92>] warn_slowpath_common+0x72/0xa0
> >> [ 1634.148659] [<c10c61f9>] ? rcu_process_callbacks+0x469/0x560
> >> [ 1634.157914] [<c10c61f9>] ? rcu_process_callbacks+0x469/0x560
> >> [ 1634.167121] [<c1039ce2>] warn_slowpath_null+0x22/0x30
> >> [ 1634.175725] [<c10c61f9>] rcu_process_callbacks+0x469/0x560
> >
> > Can't say I understand this warning ...
> >
>
> At least we are on the same page then ;-)
It looks like some rcu head list corruption ... no idea really.
> The p2p device is already removed upon stopping wpa_supplicant through
> .del_virtual_intf() callback. Took a quick peek in
> net/mac80211/iface.c:ieee80211_if_remove() and wonder whether I should
> do cfg80211_unregister_wdev() in that code path as well. Guess so, right?
I think so, yes. Does the warning go away if you do? :)
johannes
next prev parent reply other threads:[~2013-03-20 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 14:53 rcutree tree warning during P2P device support testing Arend van Spriel
2013-03-20 15:08 ` Johannes Berg
2013-03-20 21:17 ` Arend van Spriel
2013-03-20 21:29 ` Johannes Berg [this message]
2013-03-20 21:46 ` Arend van Spriel
2013-03-20 21:55 ` Johannes Berg
2013-03-21 12:04 ` Arend van Spriel
2013-03-21 12:21 ` Johannes Berg
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=1363814947.9284.10.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=dvdspndl@gmail.com \
--cc=hostap@lists.shmoo.com \
--cc=linux-wireless@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).