linux-kernel - Re: [PATCH] kmemcheck: Disable SLUB and SLAB debugging when kmemcheck is enabled

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: <1235410406.6216.69.camel@penberg-laptop>
Date:	Mon, 23 Feb 2009 19:33:26 +0200
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Christoph Lameter <cl@...ux-foundation.org>
Cc:	mingo@...e.hu, linux-kernel@...r.kernel.org,
	vegard.nossum@...il.com
Subject: Re: [PATCH] kmemcheck: Disable SLUB and SLAB debugging when
	kmemcheck is enabled

On Mon, 2009-02-23 at 10:41 -0500, Christoph Lameter wrote:
> On Mon, 23 Feb 2009, Pekka Enberg wrote:
> 
> > Enabling kmemcheck in Kconfig is a painful experience. Lets make it a
> > tad bit easier by inverting the dependencies to SLUB and SLAB debugging.
> > As kmemcheck is more powerful than slab debugging, disable the latter
> > functionality if an user enables kmemcheck.
> 
> SLUB_DEBUG is fundamentally different from SLAB_DEBUG. It only includes
> the code to be able to enable debugging at runtime. It does not enable
> debugging.

Yes, I know that but we can't really let the user enable both, slub
debugging and kmemcheck debugging, at run-time. That's why I used
SLUB_DEBUG here.

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