linux-kernel - Re: [PATCH 0/3] tools/nolibc: make all headers usable directly

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] [day] [month] [year] [list]

Message-ID: <20250424125903.GE30489@1wt.eu>
Date: Thu, 24 Apr 2025 14:59:03 +0200
From: Willy Tarreau <w@....eu>
To: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: Thomas Weißschuh <linux@...ssschuh.net>,
        Shuah Khan <shuah@...nel.org>, linux-kernel@...r.kernel.org,
        linux-kselftest@...r.kernel.org
Subject: Re: [PATCH 0/3] tools/nolibc: make all headers usable directly

Hi Thomas,

[ quick response ]

On Thu, Apr 24, 2025 at 01:48:10PM +0200, Thomas Weißschuh wrote:
> Make sure that any nolibc header can be included in any order.
> Even if nolibc.h was not pre-included already.

I've been wondering how to do this already and didn't come up with any
great solution. I think that your approach is the right one, indeed,
to include it out of the guards will force to respect ordering. That's
a great idea.  I'm all for it!

Acked-by: Willy Tarreau <w@....eu>

Willy