From: Ben Greear <greearb@candelatech.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: rusty@rustcorp.com.au, stable@kenel.org,
Joe Lawrence <joe.lawrence@stratus.com>
Subject: Please add to stable: module: don't unlink the module until we've removed all exposure.
Date: Fri, 31 May 2013 11:14:28 -0700 [thread overview]
Message-ID: <51A8E884.1080009@candelatech.com> (raw)
It turns out, the bug I spent yesterday chasing in various 3.9 kernels is apparently
fixed by the commit in the title (c9c390bb5535380d40614571894ef0c00bc026ff).
Fortunately, Joe Lawrence somehow saw my email to lkml and pointed me to the
bug report below, which mentions the commit...
https://bugzilla.kernel.org/show_bug.cgi?id=58011
Please consider adding this patch to at least the 3.9 stable queue.
I have a kernel config larded up with debugging options that reproduces
the bug fairly quickly on stock 3.9.[01234] (Fedora-17, 64-bit, in case that matters)
if someone wants it....
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2013-05-31 18:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 18:14 Ben Greear [this message]
2013-06-02 5:09 ` Please add to stable: module: don't unlink the module until we've removed all exposure Rusty Russell
2013-06-03 3:46 ` Joe Lawrence
2013-06-03 11:25 ` Joe Lawrence
2013-06-03 14:17 ` Joe Lawrence
2013-06-03 15:59 ` Ben Greear
2013-06-03 16:36 ` Ben Greear
2013-06-04 4:37 ` Rusty Russell
2013-06-04 5:56 ` Rusty Russell
2013-06-04 14:07 ` Joe Lawrence
2013-06-04 16:50 ` Joe Lawrence
2013-06-04 16:53 ` Ben Greear
2013-06-04 17:45 ` Ben Greear
2013-06-05 4:17 ` Rusty Russell
2013-06-05 7:15 ` Tejun Heo
2013-06-05 16:59 ` Ben Greear
2013-06-05 18:48 ` Tejun Heo
2013-06-05 19:11 ` Ben Greear
2013-06-05 19:31 ` stop_machine lockup issue in 3.9.y Ben Greear
2013-06-05 20:58 ` Ben Greear
2013-06-05 21:11 ` Tejun Heo
2013-06-05 21:33 ` Ben Greear
2013-06-06 1:34 ` Eric Dumazet
2013-06-06 3:14 ` Tejun Heo
2013-06-06 3:26 ` Eric Dumazet
2013-06-06 3:41 ` Ben Greear
2013-06-06 3:46 ` Eric Dumazet
2013-06-06 3:50 ` Ben Greear
2013-06-06 4:08 ` Eric Dumazet
2013-06-06 20:55 ` Tejun Heo
2013-06-06 21:15 ` Ben Greear
2013-06-06 21:17 ` Tejun Heo
2013-06-05 3:29 ` Please add to stable: module: don't unlink the module until we've removed all exposure Rusty Russell
2013-06-05 5:07 ` Greg KH
2013-06-05 7:13 ` Rusty Russell
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=51A8E884.1080009@candelatech.com \
--to=greearb@candelatech.com \
--cc=joe.lawrence@stratus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=stable@kenel.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