linux-kernel - Re: [PATCH v4 00/15] kunit: Introduce UAPI testing framework

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: <20250708073940-c2e9ee11-549b-4ef0-a480-942d86821f41@linutronix.de>
Date: Tue, 8 Jul 2025 07:51:06 +0200
From: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
To: Jonathan Corbet <corbet@....net>
Cc: Masahiro Yamada <masahiroy@...nel.org>, 
	Nathan Chancellor <nathan@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>, 
	Willy Tarreau <w@....eu>, Thomas Weißschuh <linux@...ssschuh.net>, 
	Brendan Higgins <brendan.higgins@...ux.dev>, David Gow <davidgow@...gle.com>, Rae Moar <rmoar@...gle.com>, 
	Shuah Khan <shuah@...nel.org>, Nicolas Schier <nicolas.schier@...ux.dev>, 
	Christophe Leroy <christophe.leroy@...roup.eu>, linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org, 
	linux-kselftest@...r.kernel.org, kunit-dev@...glegroups.com, linux-doc@...r.kernel.org, 
	workflows@...r.kernel.org, Kees Cook <kees@...nel.org>, 
	Alexander Viro <viro@...iv.linux.org.uk>, Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>, 
	linux-mm@...ck.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v4 00/15] kunit: Introduce UAPI testing framework

On Mon, Jul 07, 2025 at 12:18:01PM -0600, Jonathan Corbet wrote:
> Thomas Weißschuh <thomas.weissschuh@...utronix.de> writes:
> 
> > This series aims to combine kselftests and kunit, avoiding both their
> > limitations. It works by compiling the userspace kselftests as part of
> > the regular kernel build, embedding them into the kunit kernel or module
> > and executing them from there.
> 
> Please forgive the possibly dumb question but ... this series sets up
> the framework, but doesn't actually integrate the kselftests, right?

Correct.

> Will it be necessary to write a little KUnit glue function for each
> kselftest, or is there some other scheme in mind here?

With the current framework it is necessary to write some glue code:
* A stub .c file which #includes the existing kselftest source
* A kbuild userprog Makefile
* A custom KUnit function which calls kunit_uapi_run_kselftest()

A more high-level scheme may come later, but so far I have not worked on that.
It would be nice for example to build and run the tests for all ABIs supported
by a kernel without a lot of manual code duplication.
And maybe have some higher level helpers around declaring the tests.


Thomas