linux-kernel - Re: [RFC PATCH 0/9] 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: <CAFr9PX=tY6ES4-gVj5P9SA3H+ww7eQ4OAphX=sj=dPPC2M00AA@mail.gmail.com>
Date: Mon, 2 Feb 2026 06:45:40 +0900
From: Daniel Palmer <daniel@...ngy.jp>
To: Willy Tarreau <w@....eu>
Cc: linux@...ssschuh.net, kees@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/9] nolibc: Add static-pie support

Hi Willy,

On Mon, 2 Feb 2026 at 03:14, Willy Tarreau <w@....eu> wrote:
>   $ diff -u ret0*size
>   --- ret0-6.19-rc7.size  2026-02-01 19:04:33.918536545 +0100
>   +++ ret0-daniel.size    2026-02-01 19:04:40.914761767 +0100
>   @@ -16,4 +16,5 @@
>    0000000000000011 W raise
>    0000000000000012 W abort
>    0000000000000023 W memmove
>   -0000000000000098 W _start_c
>   +0000000000000086 W __start_c
>   +000000000000015f W _start_c
>
> The delta is indeed 333 bytes.
>
> Is there anything we could detect at build time to detect that we want to
> go the heavy way ? Maybe we should only condition that code to __PIE__ ?
> There's nothing critical, it's really about having an open discussion on
> this, because we're trying to keep the minimal binaries small, and here
> we're just doubling the size of the smallest ones all the time.
>
> Thanks!
> Willy

Thank you for the feedback. I'll work out a way of hiding all of the
new code unless it's needed.
I think there might still be some increase in size from splitting
_start_c() into two parts though.

Thanks,

Daniel