linux-ext4 - Re: 2.6.32-rc6 BUG at mm/slab.c:2869!

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]

Message-ID: <20090820111937.GF524@hash.localnet>
Date:	Thu, 20 Aug 2009 07:19:37 -0400
From:	Bob Copeland <me@...copeland.com>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-ext4@...r.kernel.org, Vegard Nossum <vegard.nossum@...il.com>
Subject: Re: 2.6.32-rc6 BUG at mm/slab.c:2869!

On Thu, Aug 20, 2009 at 08:08:16AM +0300, Pekka Enberg wrote:
> Someone is stomping on SLAB internal data structures. Ext4 appears in
> both stack traces so I guess we should CC linux-ext4. How easy is it
> to reproduce this bug? One option is to try kmemcheck to see if it
> catches the problem (see Documentation/kmemcheck.txt for details).

I don't yet have a way to reproduce at will but I've anecdotally hit
this or some related bug 3 times in the last week or two without trying,
I only now captured a stack trace.  I can try some workload to exercise
the filesystem a bit more to see what turns up.

I'll try that and kmemcheck next.

-- 
Bob Copeland %% www.bobcopeland.com

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html