From: Nam Le <lehoangnamtep@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
Michael Matz <matz@suse.de>,
tglx@kernel.org, mingo@redhat.com, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-toolchains@vger.kernel.org
Subject: Re: [PATCH] x86/boot: Discard .interp sections
Date: Wed, 8 Apr 2026 16:57:41 +0100 [thread overview]
Message-ID: <e2b0322e-e71b-4049-bf03-fc1e2933dfff@gmail.com> (raw)
In-Reply-To: <20260408152140.GDadZyhEaap8IK9zRt@fat_crate.local>
On 08/04/2026 16:21, Borislav Petkov wrote:
> On Wed, Apr 08, 2026 at 02:30:06PM +0100, Nam Le wrote:
>> I am hesitant on modifying the Makefile to add the --no-dynamic-linker
>> flag since a previous kernel patch proposed this exact change but was
>> rejected a while back:
>
> Ok, so how is Nix building kernels then?
>
> It sounds like they have some local fix for building the kernel.
>
I just double-checked and it seems Nix has a workaround to remove the
--dynamic-linker flag before building the kernel. As I was
hand-compiling the kernel rather than installing it from Nix, the
workaround did not get applied.
> And if so, why does the upstream kernel care?
Regarding this, I just think the difference in behavior between ld.lld
and ld.bfd is severe enough that handling this edge case is warranted.
I am happy to leave this patch out though, or add something minimal like
a conditional check to add --no-dynamic-linker if the linker is ld.lld.
next prev parent reply other threads:[~2026-04-08 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260407233957.2263551-1-lehoangnamtep@gmail.com>
2026-04-08 9:52 ` [PATCH] x86/boot: Discard .interp sections Borislav Petkov
2026-04-08 9:58 ` Segher Boessenkool
2026-04-08 10:09 ` Borislav Petkov
2026-04-08 12:01 ` Nam Le
2026-04-08 12:49 ` Borislav Petkov
2026-04-08 13:30 ` Nam Le
2026-04-08 15:21 ` Borislav Petkov
2026-04-08 15:57 ` Nam Le [this message]
2026-04-08 17:20 ` Borislav Petkov
2026-04-08 12:09 ` Michael Matz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2b0322e-e71b-4049-bf03-fc1e2933dfff@gmail.com \
--to=lehoangnamtep@gmail.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=matz@suse.de \
--cc=mingo@redhat.com \
--cc=segher@kernel.crashing.org \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox