From: Vegard Nossum <vegard.nossum@gmail.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4@vger.kernel.org
Subject: Re: 2.6.32-rc6 BUG at mm/slab.c:2869!
Date: Thu, 20 Aug 2009 14:02:49 +0200 [thread overview]
Message-ID: <19f34abd0908200502n6ff53e71ld5bc18aa581d5625@mail.gmail.com> (raw)
In-Reply-To: <20090820111937.GF524@hash.localnet>
2009/8/20 Bob Copeland <me@bobcopeland.com>:
> On Thu, Aug 20, 2009 at 08:08:16AM +0300, Pekka Enberg wrote:
>> Someone is stomping on SLAB internal data structures. Ext4 appears in
>> both stack traces so I guess we should CC linux-ext4. How easy is it
>> to reproduce this bug? One option is to try kmemcheck to see if it
>> catches the problem (see Documentation/kmemcheck.txt for details).
>
> I don't yet have a way to reproduce at will but I've anecdotally hit
> this or some related bug 3 times in the last week or two without trying,
> I only now captured a stack trace. I can try some workload to exercise
> the filesystem a bit more to see what turns up.
>
> I'll try that and kmemcheck next.
Hm, I'm afraid kmemcheck gives some known false positives related to
bitfields in ext4 code, so in the case that something turned up, it
might be hard to distinguish it from those false positives.
Sorry :-/
Vegard
next prev parent reply other threads:[~2009-08-20 12:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 1:56 Bob Copeland
2009-08-20 5:08 ` Pekka Enberg
2009-08-20 11:19 ` Bob Copeland
2009-08-20 12:02 ` Vegard Nossum [this message]
2009-08-21 2:06 ` Bob Copeland
2009-08-21 6:46 ` Vegard Nossum
2009-08-21 8:28 ` Vegard Nossum
2009-08-21 13:00 ` Eric Paris
2009-08-21 12:34 ` Eric Paris
2009-08-21 12:36 ` Bob Copeland
2009-08-21 12:39 ` Pekka Enberg
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=19f34abd0908200502n6ff53e71ld5bc18aa581d5625@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=penberg@cs.helsinki.fi \
/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®