linux-kernel - Re: 2.6.18 ext3 panic.

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 3 Oct 2006 12:45:37 -0400
From:	Dave Jones <davej@...hat.com>
To:	Andrew Morton <akpm@...l.org>, Eric Sandeen <sandeen@...deen.net>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	esandeen@...hat.com, Badari Pulavarty <pbadari@...ibm.com>,
	Jan Kara <jack@....cz>
Subject: Re: 2.6.18 ext3 panic.

On Tue, Oct 03, 2006 at 02:40:30AM -0400, Dave Jones wrote:
 
 >  > > > ----------- [cut here ] --------- [please bite here ] ---------
 >  > > > Kernel BUG at fs/buffer.c:2791
 >  > > 
 >  > > I had thought/hoped that this was fixed by Jan's patch at 
 >  > > http://lkml.org/lkml/2006/9/7/236 from the thread started at 
 >  > > http://lkml.org/lkml/2006/9/1/149, but it seems maybe not.  Dave hit this bug 
 >  > > first by going through that new codepath....
 >  > 
 >  > Yes, Jan's patch is supposed to fix that !buffer_mapped() assertion.  iirc,
 >  > Badari was hitting that BUG and was able to confirm that Jan's patch
 >  > (3998b9301d3d55be8373add22b6bc5e11c1d9b71 in post-2.6.18 mainline) fixed
 >  > it.
 > 
 > Ok, this afternoon I was definitly running a kernel with that patch in it,
 > and managed to get a trace (It was the one from the top of this thread
 > that unfortunatly got truncated).
 > 
 > Now, I can't reproduce it on a plain 2.6.18+that patch.
 > I'll leave the stress test running overnight, and see if anything
 > falls out in the morning.
 
Been chugging away for 10 hrs now without repeating that incident. Hmm.
That patch looks like good -stable material. I'll keep digging to
see if I can somehow reproduce the problem I saw with the patch applied,
but in absense of something better, I think we should go with it.

One thing that did happen in the 10hrs was fsx-over-NFS spewed some
nasty looking trace. I'll post that separately next.

	Dave

-- 
http://www.codemonkey.org.uk
-
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/