linux-kernel - Re: [PATCH] lkdtm: use SLAB_NO_MERGE instead of an empty constructor

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: <174421534033.1129976.14293587873896344735.b4-ty@kernel.org>
Date: Wed,  9 Apr 2025 09:15:42 -0700
From: Kees Cook <kees@...nel.org>
To: Harry Yoo <harry.yoo@...cle.com>
Cc: Kees Cook <kees@...nel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] lkdtm: use SLAB_NO_MERGE instead of an empty constructor

On Tue, 18 Mar 2025 10:45:33 +0900, Harry Yoo wrote:
> Use SLAB_NO_MERGE flag to prevent merging instead of providing an
> empty constructor. Using an empty constructor in this manner is an abuse
> of slab interface.
> 
> The SLAB_NO_MERGE flag should be used with caution, but in this case,
> it is acceptable as the cache is intended soley for debugging purposes.
> 
> [...]

Applied to for-next/hardening, thanks!

[1/1] lkdtm: use SLAB_NO_MERGE instead of an empty constructor
      https://git.kernel.org/kees/c/9891398efae8

Take care,

-- 
Kees Cook