linux-kernel - Re: [patch] slub: use size and objsize orders to disable debug flags

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: <4A6EAE87.9020006@cs.helsinki.fi>
Date:	Tue, 28 Jul 2009 10:53:43 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	David Rientjes <rientjes@...gle.com>
CC:	Christoph Lameter <cl@...ux-foundation.org>,
	Larry Finger <Larry.Finger@...inger.net>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Johannes Berg <johannes@...solutions.net>
Subject: Re: [patch] slub: use size and objsize orders to disable debug flags

David Rientjes wrote:
> This patch moves the masking of debugging flags which increase a cache's
> min order due to metadata when `slub_debug=O' is used from
> kmem_cache_flags() to kmem_cache_open().
> 
> Instead of defining the maximum metadata size increase in a preprocessor
> macro, this approach uses the cache's ->size and ->objsize members to
> determine if the min order increased due to debugging options.  If so,
> the flags specified in the more appropriately named DEBUG_METADATA_FLAGS
> are masked off.
> 
> This approach was suggested by Christoph Lameter
> <cl@...ux-foundation.org>.
> 
> Cc: Christoph Lameter <cl@...ux-foundation.org>
> Signed-off-by: David Rientjes <rientjes@...gle.com>

Applied, thanks!
--
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/