From: Kalle Valo <kalle.valo@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: add missing device list locking
Date: Sun, 09 Aug 2009 13:18:23 +0300 [thread overview]
Message-ID: <87iqgxl28g.fsf@litku.valot.fi> (raw)
In-Reply-To: <1249811489.4636.2.camel@johannes.local> (Johannes Berg's message of "Sun\, 09 Aug 2009 11\:51\:29 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> When calling into the wext code from the NETDEV_UP
> notifier, we need to hold the devlist_mtx mutex as
> the wext code ends up calling into channel checks.
>
> Reported-by: Kalle Valo <kalle.valo@iki.fi>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Thanks for fixing this. I wasn't able to reproduce the warning after one
suspend/resume cycle, but I'll test this patch a bit more before I send
my Tested-by tag.
--
Kalle Valo
next prev parent reply other threads:[~2009-08-09 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-09 9:51 [PATCH] cfg80211: add missing device list locking Johannes Berg
2009-08-09 10:18 ` Kalle Valo [this message]
2009-08-10 16:21 ` Kalle Valo
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=87iqgxl28g.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).