From: Andrew Morton <akpm@linux-foundation.org>
To: linux-wireless@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, Kalle Valo <kalle.valo@iki.fi>,
Jason Andryuk <jandryuk@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
karllinuxtest.relton@ntlworld.com
Subject: Re: [Bugme-new] [Bug 13312] New: at76c50x-usb mutex deadlock
Date: Thu, 28 May 2009 00:49:25 -0700 [thread overview]
Message-ID: <20090528004925.d6d9be31.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-13312-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Thu, 14 May 2009 20:54:54 GMT bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=13312
>
> Summary: at76c50x-usb mutex deadlock
> Product: Drivers
> Version: 2.5
> Kernel Version: 2.6.30-rc5
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: network-wireless
> AssignedTo: drivers_network-wireless@kernel-bugs.osdl.org
> ReportedBy: karllinuxtest.relton@ntlworld.com
> CC: kalle.valo@iki.fi
> Regression: No
>
>
> at76_dwork_hw_scan() does a mutex_lock and then calls
> ieee80211_scan_completed(). This in turn calls at76_config() which then tries
> to do the same mutex_lock and thus the driver goes into deadlock.
>
> I believe the solution would be for at76_dwork_hw_scan() to unlock the mutex
> before calling ieee80211_scan_completed(). I've tried this with my card, and it
> does indeed avoid the lockup - though I have yet to get the card working
> properly with this driver.
>
umm, is anyone looking at
drivers_network-wireless@kernel-bugs.osdl.org? This one seems a bit of
a no-brainer?
next parent reply other threads:[~2009-05-28 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13312-10286@http.bugzilla.kernel.org/>
2009-05-28 7:49 ` Andrew Morton [this message]
2009-05-28 9:45 ` [PATCH] at76c50x-usb: avoid mutex deadlock in at76_dwork_hw_scan John W. Linville
2009-06-01 13:11 ` 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=20090528004925.d6d9be31.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=jandryuk@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@iki.fi \
--cc=karllinuxtest.relton@ntlworld.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).