linux-kernel - Re: [RFC PATCH v2 02/10] tools/nolibc: crt: Split _start

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: <CAFr9PXmL_2epfEmvvwQ22O=ZvwbJV+CiEao4cxdB6CW_7ADy3g@mail.gmail.com>
Date: Sun, 8 Feb 2026 10:40:30 +0900
From: Daniel Palmer <daniel@...ngy.jp>
To: Willy Tarreau <w@....eu>
Cc: linux@...ssschuh.net, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2 02/10] tools/nolibc: crt: Split _start_c() into
 stack-only and normal parts

Hi Willy,

On Sun, 8 Feb 2026 at 00:45, Willy Tarreau <w@....eu> wrote:
> > +#if __nolibc_has_feature(undefined_behavior_sanitizer)
> > +#  define __no_sanitize __attribute__((no_sanitize("function")))
> > +#else
> > +#  define __no_sanitize
> > +#endif
>
> I'm starting to feel uncomfortable with the addition of new __no_foo
> stuff, which doesn't have the "nolibc" prefix, risking to conflict with
> userland code. I think we'll have to go through a cleanup patch at some
> point for __no_sanitize and __no_stack_protector.
>
> So probably in order to reduce the technical debt it would be nice to
> to prepend __nolibc in front of this new internal macro. Maybe this part
> of the patch should be a separate cleanup patch by the way, as future
> patches might depend on it.

Since this relocation thing will still take more time I will create a
set of patches just to add the prefix to __no_stack_protector, add
__nolibc_no_sanitize and use it in crt.h to send now instead of as
part of this.

Cheers,

Daniel