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:55:48 +0100 [thread overview]
Message-ID: <1363816548.9284.11.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <514A2E47.7080108@broadcom.com>
On Wed, 2013-03-20 at 22:46 +0100, Arend van Spriel wrote:
> > It looks like some rcu head list corruption ... no idea really.
> >
>
> I have now (I think). I did a kfree of the driver's vif structure, which
> is container of the wireless_dev and that is still on the rcu head list.
I don't really see why that would be the case though, there's no
call_rcu() or kfree_rcu(), is there?
johannes
next prev parent reply other threads:[~2013-03-20 21:55 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
2013-03-20 21:46 ` Arend van Spriel
2013-03-20 21:55 ` Johannes Berg [this message]
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=1363816548.9284.11.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.