From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Arnd Bergmann <arnd@arndb.de>,
LKML <linux-kernel@vger.kernel.org>,
Kay Sievers <kay.sievers@vrfy.org>,
Brandon Philips <brandon@ifup.org>
Subject: Re: [BUG 2.6.36-rc6] list corruption in module_bug_finalize
Date: Tue, 5 Oct 2010 19:43:33 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1010051923140.2556@localhost6.localdomain6> (raw)
In-Reply-To: <AANLkTinCgGDxhuUf1a+gO-xdVi9bU0Shmo-KejC+eU4o@mail.gmail.com>
On Tue, 5 Oct 2010, Linus Torvalds wrote:
> On Tue, Oct 5, 2010 at 9:40 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> >
> > Hmm, with this patch the corruption triggers at every boot (5 of
> > 5). Without it it's just happening randomly (1 of 10)
> >
> > Digging further. Dammit, I fear my evil plan fires back now due to
> > some even more lazy person who doesn't use modules. :)
>
> Sre you sure you used the second version? The first version missed the
> cleanup at module unload time, and would have caused the symptoms you
> see.
Crap, yes. Stupid me managed to pick the wrong one though I'm sure I
double checked.
> I just tried my own machine with modules (and list debugging), and it
> seemed fine. And it show now all happen under the module mutex, so I
> don't see how it would be timing-sensitive.
>
> But hey, maybe I'm missing something really silly.
Nah. Works fine. Sorry for making you build modules :)
Tested-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2010-10-05 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 19:51 Thomas Gleixner
2010-10-04 11:00 ` Arnd Bergmann
2010-10-04 22:43 ` Thomas Gleixner
2010-10-04 23:55 ` Linus Torvalds
2010-10-05 1:11 ` Linus Torvalds
2010-10-05 5:14 ` Rusty Russell
2010-10-05 7:30 ` Thomas Gleixner
2010-10-05 15:34 ` Linus Torvalds
2010-10-05 16:40 ` Thomas Gleixner
2010-10-05 17:17 ` Linus Torvalds
2010-10-05 17:43 ` Thomas Gleixner [this message]
2010-10-06 9:10 ` Rusty Russell
2010-10-05 4:18 ` Rusty Russell
2010-10-05 11:08 ` Adrian Bunk
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=alpine.LFD.2.00.1010051923140.2556@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=arnd@arndb.de \
--cc=brandon@ifup.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®