linux-kernel - Re: [PATCH] mm/slab_common: Support the slub_debug boot option on specific object size

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: <alpine.DEB.2.11.1504201040010.2264@gentwo.org>
Date:	Mon, 20 Apr 2015 10:40:36 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	Gavin Guo <gavin.guo@...onical.com>
cc:	penberg@...nel.org, rientjes@...gle.com, iamjoonsoo.kim@....com,
	akpm@...ux-foundation.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/slab_common: Support the slub_debug boot option on
 specific object size

On Sat, 18 Apr 2015, Gavin Guo wrote:

> The slub_debug=PU,kmalloc-xx cannot work because in the
> create_kmalloc_caches() the s->name is created after the
> create_kmalloc_cache() is called. The name is NULL in the
> create_kmalloc_cache() so the kmem_cache_flags() would not set the
> slub_debug flags to the s->flags. The fix here set up a temporary
> kmalloc_names string array for the initialization purpose. After the
> kmalloc_caches are already it can be used to create s->name in the
> kasprintf.

Ok if you do that then the dynamic creation of the kmalloc hostname can
also be removed. This patch should do that as well.
--
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/