linux-kernel - Re: Oops 2.6.23.1 in ext3+jbd at journal_put_journal

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4739ED3C.6090809@rtr.ca>
Date:	Tue, 13 Nov 2007 13:30:20 -0500
From:	Mark Lord <lkml@....ca>
To:	Jan Kara <jack@...e.cz>
Cc:	linux-ext4@...r.kernel.org,
	Linux Kernel <linux-kernel@...r.kernel.org>, sct@...hat.com,
	akpm@...ux-foundation.org, adilger@...sterfs.com
Subject: Re: Oops 2.6.23.1 in ext3+jbd at journal_put_journal_head

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/