linux-kernel - Re: [RFC PATCH v2 00/10] nolibc: Add static-pie support

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: <CAFr9PXmEYnM1_KSORNXc3TNSMO=m2hkLr3rxkbvKgYqy07QfUw@mail.gmail.com>
Date: Sun, 8 Feb 2026 10:35:14 +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 00/10] nolibc: Add static-pie support

Hi Willy,

Thank you for taking the time to look at this.

On Sun, 8 Feb 2026 at 00:34, Willy Tarreau <w@....eu> wrote:
> If you absolutely need to forcefully inline, you should add
> __attribute__((always_inline)) in addition to __inline__, as
> it will override the default compiler setting based on the
> optimization level. However the functions are short enough
> that they were always inlined in my tests regardless of the
> attribute.

Noted. Like you said I think the functions always get inlined so the
problem is theoretical.
I think actually just disabling the stack projector for the functions
will be enough if the compiler ever decides not to inline.
I guess I'll try the opposite and force the compiler not to inline and
see if it breaks.

Thanks,

Daniel