From: Johannes Berg <johannes@sipsolutions.net>
To: seventh guardian <seventhguardian@gmail.com>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: d80211 deadlock with wpa_supplicant and rmmod
Date: Fri, 13 Jul 2007 23:45:16 +0200 [thread overview]
Message-ID: <1184363116.3928.4.camel@johannes.berg> (raw)
In-Reply-To: <1caff7430707130505r579ef08cmacc6c77f7535a66c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
On Fri, 2007-07-13 at 13:05 +0100, seventh guardian wrote:
> Hello, sorry for the delay but I only managed to try it out today..
> I've applied the patch and tortured the system as far as I could, and
> no hang at all :)
>
> I've read the thread and it apparently replaces one bad problem for a
> lesser one, so I understand if it's not applied.. But at least there
> is a place in the code to point as the culprit :)
It definitely should be applied anyway :) I guess John just hasn't
caught up with all threads yet.
John: This is about the patch in the "mac80211/bcm43xx deadlock" thread
from Michael, it kills some rtnl_lock()/unlock() that causes this
deadlock.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2007-07-13 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1caff7430707111617o70a534a5x2cf6b611a91f301a@mail.gmail.com>
2007-07-11 23:41 ` d80211 deadlock with wpa_supplicant and rmmod John W. Linville
2007-07-12 2:20 ` seventh guardian
2007-07-12 10:02 ` Johannes Berg
2007-07-13 12:05 ` seventh guardian
2007-07-13 21:45 ` Johannes Berg [this message]
2007-07-14 13:24 ` Jiri Benc
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=1184363116.3928.4.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=seventhguardian@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