From: Larry Finger <Larry.Finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Luca Niccoli <lultimouomo@gmail.com>,
linux-wireless@vger.kernel.org, stable@kernel.org
Subject: Re: Please backport [PATCH] rtl8187: Fix kernel oops when device is removed when LEDS enabled (Bugzilla #14539)
Date: Tue, 10 Nov 2009 10:18:06 -0600 [thread overview]
Message-ID: <4AF9923E.9020603@lwfinger.net> (raw)
In-Reply-To: <20091110155511.GE12682@tuxdriver.com>
On 11/10/2009 09:55 AM, John W. Linville wrote:
> On Tue, Nov 10, 2009 at 04:47:50PM +0100, Luca Niccoli wrote:
>> I'm running 2.6.31 (from debian source) and I experienced hard freezes
>> on removing the module or disconnecting the USB card.
>> The patch at [1] seems to have fixed the problem, so it would be nice
>> if it could be included in the 2.6.31 branch.
>> Note that I was not experiencing the freezes with the distribution
>> kernel, just with a self compiled one (without source modifications
>> though, only config).
>> Cheers,
>>
>> Luca
>>
>> (For further info please Cc: me)
>>
>> [1]
>> http://marc.info/?l=linux-wireless&m=125731443329754&w=2
>
> This has already been sent with the proper tagging to make the stable
> crew aware of it...
>
> Thanks,
>
> John
>
> commit 37b12dd2b07b4d7dc222a5f7f88b25cec532b2aa
> Author: Larry Finger <Larry.Finger@lwfinger.net>
> Date: Wed Nov 4 00:00:25 2009 -0600
>
> rtl8187: Fix kernel oops when device is removed when LEDS enabled
>
> As reported by Rick Farina (sidhayn@gmail.com), removing the RTL8187
> USB stick, or unloading the driver rtl8187 using rmmod will cause a
> kernel oops. There are at least two forms of the failure, (1) BUG:
> Scheduling while atomic, and (2) a fatal kernel page fault. This
> problem is reported in Bugzilla #14539.
>
> This problem does not occur for kernel 2.6.31, but does for 2.6.32-rc2,
> thus it is technically a regression; however, bisection did not locate
> any faulty patch. The fix was found by comparing the faulty code in
> rtl8187 with p54usb. My interpretation is that the handling of work
> queues in mac80211 changed enough to the LEDs to be unregistered
> before tasks on the work queues are cancelled. Previously, these
> actions could be done in either order.
>
> (Herton Ronaldo Krzesinski <herton@mandriva.com.br> reports that the
> code is the same in 2.6.31, so this may be a candidate for 2.6.31.x.
> -- JWL)
>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Reported-by: Rick Farina <sidhayn@gmail.com>
> Tested-by: Rick Farina <sidhayn@gmail.com>
> Cc: stable@kernel.org
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Additionally, that patch has just made it to mainline. It was not there until I
did a git pull this morning.
Larry
next prev parent reply other threads:[~2009-11-10 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 15:47 Please backport [PATCH] rtl8187: Fix kernel oops when device is removed when LEDS enabled (Bugzilla #14539) Luca Niccoli
2009-11-10 15:55 ` John W. Linville
2009-11-10 16:18 ` Larry Finger [this message]
2009-11-10 16:14 ` Larry Finger
2009-11-10 16:33 ` Luca Niccoli
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=4AF9923E.9020603@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lultimouomo@gmail.com \
--cc=stable@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).