| 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
| ||
|
Message-ID: <19f34abd0908200502n6ff53e71ld5bc18aa581d5625@mail.gmail.com> Date: Thu, 20 Aug 2009 14:02:49 +0200 From: Vegard Nossum <vegard.nossum@...il.com> To: Bob Copeland <me@...copeland.com> Cc: Pekka Enberg <penberg@...helsinki.fi>, linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, linux-ext4@...r.kernel.org Subject: Re: 2.6.32-rc6 BUG at mm/slab.c:2869! 2009/8/20 Bob Copeland <me@...copeland.com>: > 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. Hm, I'm afraid kmemcheck gives some known false positives related to bitfields in ext4 code, so in the case that something turned up, it might be hard to distinguish it from those false positives. Sorry :-/ Vegard -- 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
Powered by blists - more mailing lists