linux-kernel - Re: [PATCH] SLUB: clear c->freelist in __slab_alloc()/load

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: <482B2752.2090600@panasas.com>
Date:	Wed, 14 May 2008 10:54:26 -0700
From:	Benny Halevy <bhalevy@...asas.com>
To:	Christoph Lameter <clameter@....com>,
	Pekka Enberg <penberg@...helsinki.fi>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] SLUB: clear c->freelist in __slab_alloc()/load_freelist:/SlabDebug
 path

On May. 14, 2008, 10:44 -0700, Christoph Lameter <clameter@....com> wrote:
> On Tue, 13 May 2008, Benny Halevy wrote:
> 
>>> But for debug pages, we never load c->page->freelist to c->freelist so
>>> it should always be NULL.
>> Hmm, I see.  Then it might have got corrupted...
>> I'll keep looking for the root cause.
> 
> Correct.

Yeah, I've moved to SLAB and the mem corruption now pops up at a different
place.

> 
>>> How did you make SLUB hit the debug path since you have
>>> CONFIG_SLUB_DEBUG_ON disabled?
> 
> I guess he passed slub_debug on the kernel command line.
> 

I did not.

I probably have misunderstood how the slub debugging infrastructure works
and did not execute the debug path at all.

Thanks for your help!

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