linux-kernel - Re: repeatable slab corruption with LTP msgctl08

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080612122009.f4d3a82a.akpm@linux-foundation.org>
Date:	Thu, 12 Jun 2008 12:20:09 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Manfred Spraul <manfred@...orfullife.com>
Cc:	penberg@...helsinki.fi, Nadia.Derbey@...l.net,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org, clameter@....com
Subject: Re: repeatable slab corruption with LTP msgctl08

On Thu, 12 Jun 2008 21:09:10 +0200
Manfred Spraul <manfred@...orfullife.com> wrote:

> Either someone does a set_bit() or your cpu is breaking down.

Well.  It is about ten years old.  But this is the first sign of a
problem and it's always msgctl08.

>  From looking at the the msgctl08 test: it shouldn't produce any races, 
> it just does lots of bulk msgsnd()/msgrcv() operations. Always one 
> thread sends, one thread receives on each queue. It's probably more a 
> scheduler stresstest than anything else.
> 
> Attached is a completely untested patch:
> - add 8 bytes to each slabp struct: This changes the alignment of the 
> bufctl entries.
> - add a hexdump of the redzone bytes.

OK, I'll try that this evening (eight hours hence).

I'll also try increasing /proc/sys/kernel/msgmni under 2.6.25.

> Andrew: how do you log the oops? 
> it might scroll of the screen.

netconsole-to-disk.

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