linux-kernel - Re: [PATCH 00/16] selftests: vDSO: parse

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250222102626.GB13708@1wt.eu>
Date: Sat, 22 Feb 2025 11:26:26 +0100
From: Willy Tarreau <w@....eu>
To: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: Christophe Leroy <christophe.leroy@...roup.eu>,
        Kees Cook <kees@...nel.org>, Eric Biederman <ebiederm@...ssion.com>,
        Shuah Khan <shuah@...nel.org>, Nathan Chancellor <nathan@...nel.org>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        Bill Wendling <morbo@...gle.com>,
        Justin Stitt <justinstitt@...gle.com>,
        Andy Lutomirski <luto@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Vincenzo Frascino <vincenzo.frascino@....com>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
        llvm@...ts.linux.dev
Subject: Re: [PATCH 00/16] selftests: vDSO: parse_vdso: Make compatible with
 nolibc

On Mon, Feb 03, 2025 at 05:14:37PM +0100, Thomas Weißschuh wrote:
> On Mon, Feb 03, 2025 at 04:43:22PM +0100, Christophe Leroy wrote:
> <snip>
> 
> > Do you have any plan to get it work with nolibc for all test programs in
> > selftests/vDSO, not only the standalone x86 test ?
> 
> Not directly as next step. I am focussing on some other work which will
> integrate (vDSO) selftests with nolibc slightly differently.
> However if you have interest in converting the tests now, that would be
> great and will also be useful for my future changes.
> The current issues I see:
> * Missing architecture support in nolibc (should be fairly easy to implement)
> * Missing kselftest_harness.h support in nolibc (I'm working on that)
> * Maybe some users want to stick with their regular libc
>   (Nothing should prevent that, but the mechanism may need some discussion)

BTW, I wanted to thank you for this work. Originally when I started with
nolibc, I thought the vdso was out of reach due to the many missing
definitions. Turns out you were braver than me ;-)

Cheers,
Willy