From: Mark Lord <lkml@rtr.ca>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
sct@redhat.com, akpm@linux-foundation.org, adilger@clusterfs.com
Subject: Re: Oops 2.6.23.1 in ext3+jbd at journal_put_journal_head
Date: Tue, 13 Nov 2007 13:30:20 -0500 [thread overview]
Message-ID: <4739ED3C.6090809@rtr.ca> (raw)
In-Reply-To: <20071113172130.GA13733@atrey.karlin.mff.cuni.cz>
Jan Kara wrote:
> Hello,
>
>> A one-time event thus far, happened under very heavy I/O,
>> Dell i9400 Core2Duo notebook w/3GB ram, single SATA drive with ext3.
>> Had to cycle power to get it back and see this Oops in the syslog:
..
> Hmm, your pointer to buffer_head in journal_head has been overwritten
> by some garbage - it actually looks like ASCII ("C\n ra"). I think your
> journal_head pointer is stored in EAX (at least if I compile SMP kernel
> for i386 it is) and that is 0xc2bd7000 - start of the page. So probably
..
As for me, I'm guessing a use/free race somewhere, but with
only the information from the Oops that's hard to know.
> some driver went wild and overwritten a piece of memory which did not
> belong to it... I suggest turning on a few debugging options (like
> DEBUG_SLAB) to catch the offender.
..
You mean, like, this:
> #
> # Automatically generated make config: don't edit
> # Linux kernel version: 2.6.23.1-slab
> # Wed Nov 7 08:00:18 2007
> #
> CONFIG_X86_32=y
...
> CONFIG_DEBUG_SLAB=y
...
Thought since it was..
> A one-time event thus far ...
..
.. I'm unlikely to see it again.
Cheers
prev parent reply other threads:[~2007-11-13 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 19:40 Oops 2.6.23.1 in ext3+jbd at journal_put_journal_head Mark Lord
2007-11-12 19:40 ` Mark Lord
2007-11-12 19:41 ` Mark Lord
2007-11-13 17:21 ` Jan Kara
2007-11-13 18:30 ` Mark Lord [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=4739ED3C.6090809@rtr.ca \
--to=lkml@rtr.ca \
--cc=adilger@clusterfs.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
/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.