From: Eric Sandeen <sandeen@sandeen.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18-1.2689.fc6PAE: oops in ext3_clear_inode+0x52/0x8b
Date: Tue, 03 Oct 2006 11:27:47 -0500 [thread overview]
Message-ID: <45228F83.1000309@sandeen.net> (raw)
In-Reply-To: <20061003162313.GA7398@stusta.de>
Adrian Bunk wrote:
> Another tainted kernel...
Yes. One was tainted with a force, and another tainted with proprietary
modules.
I was quick to dismiss the first one due to the taint, but the
likelihood of both taints being the root cause of the exact same
corruption seems low. Still, nigh impossible to work with.
-Eric
prev parent reply other threads:[~2006-10-03 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 20:42 2.6.18-1.2689.fc6PAE: oops in ext3_clear_inode+0x52/0x8b Jeremy Fitzhardinge
2006-09-28 20:48 ` James Morris
2006-09-28 21:00 ` Jeremy Fitzhardinge
2006-09-28 21:23 ` Andrew Morton
2006-09-28 21:26 ` Jeremy Fitzhardinge
2006-10-03 5:32 ` Eric Sandeen
2006-10-03 5:42 ` Adrian Bunk
2006-10-03 14:06 ` Eric Sandeen
2006-10-03 16:23 ` Adrian Bunk
2006-10-03 16:27 ` Eric Sandeen [this message]
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=45228F83.1000309@sandeen.net \
--to=sandeen@sandeen.net \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@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