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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.11.1504210905540.20333@gentwo.org>
Date:	Tue, 21 Apr 2015 09:06:07 -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 <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm/slab_common: Support the slub_debug boot option on
 specific object size

On Tue, 21 Apr 2015, Gavin Guo wrote:

> Thanks for your reply. I put the kmalloc_names in the __initdata
> section. And it will be cleaned. Do you think the kmalloc_names should
> be put in the global data section to avoid the dynamic creation of the
> kmalloc hostname again?

Yes.

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