From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Repeatable ext4 oops with 3.6.0 (regression)
Date: Thu, 04 Oct 2012 23:11:21 +0200 [thread overview]
Message-ID: <506DFB79.1040307@googlemail.com> (raw)
In-Reply-To: <20121004173425.GA15405@thunk.org>
(dear -mm: please see
http://thread.gmane.org/gmane.comp.file-systems.ext4/34665 for the
origins of this oops)
On 10/04/12 19:34, Theodore Ts'o wrote:
> On Thu, Oct 04, 2012 at 05:31:41PM +0200, Holger Hoffstätte wrote:
>
>> So armed with multiple running shells I finally managed to save the dmesg
>> to NFS. It doesn't get any more complete than this and again shows the
>> ext4 stacktrace from before. So maybe it really is generic kmem corruption
>> and ext4 looking at symlinks/inodes is just the victim.
>
> That certainly seems to be the case. As near as I can tell from the
Good to know. Unfortunately I'm still at a loss why apparently only
gthumb can trigger this; I had not noticed any other problems with 3.6.0
before that (ran it for half a day, desktop use).
> So it's very likely that the crash in __kmalloc() is probably caused
> by the internal slab/slub data structures getting scrambled.
For giggles I rebuilt with SLAB instead of SLUB, but no luck; same
segfault and delayed oopsie. I also collected an strace, but I cannot
really see anything out of the ordinary - it starts, loads things,
traverses directories and then segfaults.
I've put the earlier full dmesg and the strace into
http://hoho.dyndns.org/~holger/ext4-oops-3.6.0/ - maybe it helps someone
else.
Any suggestions for memory debugging? I saw several options in the
kernel config (under "Kernel Hacking") but was not sure what to enable.
Holger
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Repeatable ext4 oops with 3.6.0 (regression)
Date: Thu, 04 Oct 2012 23:11:21 +0200 [thread overview]
Message-ID: <506DFB79.1040307@googlemail.com> (raw)
In-Reply-To: <20121004173425.GA15405@thunk.org>
(dear -mm: please see
http://thread.gmane.org/gmane.comp.file-systems.ext4/34665 for the
origins of this oops)
On 10/04/12 19:34, Theodore Ts'o wrote:
> On Thu, Oct 04, 2012 at 05:31:41PM +0200, Holger Hoffstatte wrote:
>
>> So armed with multiple running shells I finally managed to save the dmesg
>> to NFS. It doesn't get any more complete than this and again shows the
>> ext4 stacktrace from before. So maybe it really is generic kmem corruption
>> and ext4 looking at symlinks/inodes is just the victim.
>
> That certainly seems to be the case. As near as I can tell from the
Good to know. Unfortunately I'm still at a loss why apparently only
gthumb can trigger this; I had not noticed any other problems with 3.6.0
before that (ran it for half a day, desktop use).
> So it's very likely that the crash in __kmalloc() is probably caused
> by the internal slab/slub data structures getting scrambled.
For giggles I rebuilt with SLAB instead of SLUB, but no luck; same
segfault and delayed oopsie. I also collected an strace, but I cannot
really see anything out of the ordinary - it starts, loads things,
traverses directories and then segfaults.
I've put the earlier full dmesg and the strace into
http://hoho.dyndns.org/~holger/ext4-oops-3.6.0/ - maybe it helps someone
else.
Any suggestions for memory debugging? I saw several options in the
kernel config (under "Kernel Hacking") but was not sure what to enable.
Holger
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-10-04 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 11:19 Repeatable ext4 oops with 3.6.0 (regression) Holger Hoffstaette
2012-10-02 13:36 ` Jan Kara
2012-10-02 14:31 ` Holger Hoffstaette
2012-10-04 13:01 ` Jan Kara
2012-10-04 13:01 ` Jan Kara
2012-10-04 15:31 ` Holger Hoffstätte
2012-10-04 16:12 ` Lee Schermerhorn
2012-10-04 16:12 ` Lee Schermerhorn
2012-10-04 17:34 ` Theodore Ts'o
2012-10-04 21:11 ` Holger Hoffstätte [this message]
2012-10-04 21:11 ` Holger Hoffstätte
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=506DFB79.1040307@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.