linux-kernel - Re: [PATCH] LANDLOCK: use kmem_cache for landlock

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: <2024032836-grief-parish-88e7@gregkh>
Date: Thu, 28 Mar 2024 07:08:04 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Ayush Tiwari <ayushtiw0110@...il.com>
Cc: alison.schofield@...el.com, paul@...l-moore.com, mic@...ikod.net,
	fabio.maria.de.francesco@...ux.intel.com,
	linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org,
	outreachy@...ts.linux.dev, linux-security-module@...r.kernel.org
Subject: Re: [PATCH] LANDLOCK: use kmem_cache for landlock_object

On Thu, Mar 28, 2024 at 04:55:57AM +0530, Ayush Tiwari wrote:
> Use kmem_cache replace kzalloc() calls with kmem_cache_zalloc() for
> struct landlock_object and update the related dependencies.

This says what you do, but not why you want to do any of this.  Why is
this change needed?  What benifit does it bring?

And why did you cc: the staging mailing list?

thanks,

greg k-h