linux-kernel - Re: [PATCH v4 06/15] fs,fork,exit: export symbols necessary for KUnit UAPI support

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: <aHeIyNmIYsKkBktV@infradead.org>
Date: Wed, 16 Jul 2025 04:11:04 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: Christoph Hellwig <hch@...radead.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Luis Chamberlain <mcgrof@...nel.org>, Kees Cook <kees@...nel.org>,
	Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
	linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 06/15] fs,fork,exit: export symbols necessary for
 KUnit UAPI support

On Wed, Jul 16, 2025 at 10:39:57AM +0200, Thomas Weißschuh wrote:
> Let's take kernel_execve() as example, there is no way around using this
> function in one way or another. It only has two existing callers.
> init/main.c: It is completely unsuitable for this usecase.
> kernel/umh.c: It is also what Al suggested and I am all for it.
> Unfortunately it is missing features. Citation from my response to Al:

But why does the code that calls it need to be modular?  I get why
the actual test cases should be modular, but the core test runner is
small and needs a lot of kernel internals.  Just require it to be
built-in and all this mess goes away.

That being said some of this stuff, like get_fs_type / put_filesystem
or replace_fd seem like the wrong level of abstractions for something
running tests anyway.