linux-kernel - Re: [Bug 13631] BUG/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>] [day] [month] [year] [list]

Message-ID: <4A4F5211.10806@cs.helsinki.fi>
Date:	Sat, 04 Jul 2009 15:58:57 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	bugzilla-daemon@...zilla.kernel.org,
	LKML <linux-kernel@...r.kernel.org>, bplant@...et.net.au,
	Andrew Morton <akpm@...ux-foundation.org>, mfasheh@...e.com,
	joel.becker@...cle.com
Subject: Re: [Bug 13631] BUG/panic - update_curr

Hi Brad,

bugzilla-daemon@...zilla.kernel.org wrote:
> --- Comment #14 from Brad Plant <bplant@...et.net.au>  2009-07-03 15:23:06 ---
> Created an attachment (id=22193)
>  --> (http://bugzilla.kernel.org/attachment.cgi?id=22193)
> BUG kmalloc-16: Redzone overwritten
> 
> (In reply to comment #13)
>> Looking at the bug report, I'd be pretty surprised if this would be a
>> SLUB bug. It seems more likely that there's some memory corruption going
>> on under heavy load and SLAB just happens to have a different layout of
>> slab objects or something.
>>
>> Did you run the test with CONFIG_SLAB_DEBUG, btw?
> 
> I tried slub debugging first. I tried to make it crash for a while but of
> course it wouldn't do it when I wanted it to. I had given up on trying to crash
> slub and was just rebooting the node to change the kernel when I hit the
> jackpot.
> 
> Does this suggest ocfs2 is corrupting the memory?

Yup, that would be the prime suspect here. Lets cc ocfs2 developers and 
LKML. The corruption can be found here:

   http://bugzilla.kernel.org/attachment.cgi?id=22193

			Pekka
--
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/