Date: Mon, 30 Jun 2003 11:19:26 -0700
From: Andrew Morton <akpm@digeo.com>
To: maneesh@in.ibm.com
Cc: mbligh@aracnet.com, James.Bottomley@SteelEye.com,
       linux-kernel@vger.kernel.org
Subject: Re: 2.5.73-mm1 falling over in SDET
Message-Id: <20030630111926.5d883a3b.akpm@digeo.com>
In-Reply-To: <20030630130432.GD4065@in.ibm.com>
References: <20030628170235.51ee2f69.akpm@digeo.com>
	<1056857338.2514.4.camel@mulgrave>
	<6620000.1056864944@[10.10.2.4]>
	<20030630101719.GC4065@in.ibm.com>
	<20030630130432.GD4065@in.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1095
Lines: 27

Maneesh Soni <maneesh@in.ibm.com> wrote:
>
> > I tried sdet on 16-way numaq with 2.5.73-mm2. It completes the run on ext2 
> > (no OOMs), but gives following oops while running on ext3
> > 
> 
> Looks like that was some one off oops.. on second iteration I could run
> sdet on ext3 also without any oops or oom.

No, I think that assertion failure in journal_dirty_metadata() was more
than a once off, whatever that is.  There is probably something wrong in
there, but from a moderate-sized look I cannot see what it is.

Unless inspiration strikes we will need to wait until someone can hit it
with some sort of repeatability and then run with the ext3-debug patch
applied and enabled.

http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.73/ext3-debug.patch

This will give a trace of what happened to that buffer and should allow me
to fix the bug.

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