linux-kernel - Re: 2.6.21-rc5-mm4 (SLUB)

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:	Wed, 4 Apr 2007 11:04:32 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Badari Pulavarty <pbadari@...il.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.21-rc5-mm4 (SLUB)

On Wed, 4 Apr 2007, Badari Pulavarty wrote:

> Machine booted fine with slub_debug=F. Got following in the
> log. I guess we need to track down who is touching after
> free. Any ideas on how I can track down easily ? Is there
> a way to store last allocated (function, line#) and look
> around there ?

Yes. slub_debug=U. But user tracking may need to increase the slab 
size (depends on the padding available in the slab) to store the 
tracking information, so you may not get the same corruption.

> *** SLUB: Freepointer corrupt in kmalloc-16@...fff810173f172a0 Slab
> 0xffff81017f9f8b80
>     offset=672 flags=0x2000000000000c7 inuse=42
> freelist=0xffff810173f172a0
>   Bytes b4 0xffff810173f17290:  a0 72 f1 73 00 00 00 00 00 00 00 00 00
> 00 00 00 .r\uffffs............
>     Object 0xffff810173f172a0:  00 00 00 00 01 81 ff ff 00 00 00 00 00
> 00 00 00 ......\uffff\uffff........
> FreePointer 0xffff810173f172a0 -> 0xffff810100000000

Same as before.
-
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/