linux-kernel - Re: [PATCH v2 0/2] nolibc: remove reliance on system headers

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: <20230831041202.5896-1-falcon@tinylab.org>
Date:   Thu, 31 Aug 2023 12:12:02 +0800
From:   Zhangjin Wu <falcon@...ylab.org>
To:     w@....eu
Cc:     falcon@...ylab.org, linux-kernel@...r.kernel.org,
        linux-kselftest@...r.kernel.org, linux@...ssschuh.net,
        shuah@...nel.org, tanyuan@...ylab.org
Subject: Re: [PATCH v2 0/2] nolibc: remove reliance on system headers

Hi, Willy

> On Wed, Aug 30, 2023 at 05:07:11PM +0200, Thomas Weißschuh wrote:
> > This was prompted by the discussion about output directory support with
> > O=.
> > It seems sometimes we were pulling in system headers making testing
> > annoying and unreliable.
> > 
> > Willy:
> > 
> > I did not implement the '#ifdef va_start` guard that we discussed
> > before. In my understanding the latest agreement does not need it
> > anymore. Please let me know if this is incorrect.
> 
> No that's fine given your goal of including just "nolibc.h" and no
> other regular include file, I agree. I've just merged it and pushed
> it to the -next branch.
>
> Thank you Thomas!
> Willy
> 
> Subject: [PATCH v2 1/2] tools/nolibc: add stdarg.h header
> 
> This allows nolic to work with `-nostdinc` avoiding any reliance on
> system headers.
>

A little typo in above commit message: nolic -> nolibc.

Thanks,
Zhangjin

> The implementation has been lifted from musl libc 1.2.4.
> There is already an implementation of stdarg.h in include/linux/stdarg.h
> but that is GPL licensed and therefore not suitable for nolibc.
> 
> The used compiler builtins have been validated to be at least available
> since GCC 4.1.2 and clang 3.0.0.