linux-kernel - Re: [PATCH 00/32] kselftest harness and nolibc compatibility

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: <20250304080656.GF9911@1wt.eu>
Date: Tue, 4 Mar 2025 09:06:56 +0100
From: Willy Tarreau <w@....eu>
To: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: Shuah Khan <shuah@...nel.org>, Shuah Khan <skhan@...uxfoundation.org>,
        Thomas Weißschuh <linux@...ssschuh.net>,
        linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH 00/32] kselftest harness and nolibc compatibility

Hi Thomas,

On Tue, Mar 04, 2025 at 08:10:30AM +0100, Thomas Weißschuh wrote:
> Nolibc is useful for selftests as the test programs can be very small,
> and compiled with just a kernel crosscompiler, without userspace support.
> Currently nolibc is only usable with kselftest.h, not the more
> convenient to use kselftest_harness.h
> This series provides this compatibility by adding new features to nolibc
> and removing the usage of problematic features from the harness.
> 
> The first half of the series are changes to the harness, the second one
> are for nolibc. Both parts are very independent and can go through
> different trees.
> The last patch is not meant to be applied and serves as test that
> everything works correctly.
> 
> Based on the next branch of the nolibc tree:
> https://web.git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git/log/?h=next

Really nice work, thank you, particularly for making the waitpid() and
printf() families more standard. Please accept my Acked-by on all the
nolibc parts. As usual, proceed as you see fit for the ones I commented
and assume the Acked-by for adjustments following the same spirit ;-)

Cheers,
Willy