From: Michael Matz <matz@suse.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
Nam Le <lehoangnamtep@gmail.com>,
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 14:09:09 +0200 (CEST) [thread overview]
Message-ID: <30d52592-644c-1ff2-e610-357d42461121@suse.de> (raw)
In-Reply-To: <20260408100944.GBadYpaB8WLl78FamY@fat_crate.local>
Hello,
On Wed, 8 Apr 2026, Borislav Petkov wrote:
> On Wed, Apr 08, 2026 at 04:58:08AM -0500, Segher Boessenkool wrote:
> > On Wed, Apr 08, 2026 at 11:52:02AM +0200, Borislav Petkov wrote:
> > > Sounds to me like you're shooting yourself in the foot on purpose:
> >
> > And no matter what this needs to add a comment there saying this is to
> > work around, hrm, imperfections in LLVM! So that people who hit
> > problems here later have something to start with.
>
> Right, I see --dynamic-linker=file in ld.bfd too. Why isn't that one slapping
> a section too?
It does normally. (See any random executable file in /bin/)
But section layout can and does differ between ld.bfd and ld.lld (and for
bfd it depends on the linker script), so it's probably simply not getting
in the way of your explicitely placed sections with ld.bfd. You might be
interested in --no-dynamic-linker or -static, no idea what the current
needs of the kernel vmlinux image are.
Ciao,
Michael.
prev parent reply other threads:[~2026-04-08 12:09 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
2026-04-08 17:20 ` Borislav Petkov
2026-04-08 12:09 ` Michael Matz [this message]
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=30d52592-644c-1ff2-e610-357d42461121@suse.de \
--to=matz@suse.de \
--cc=bp@alien8.de \
--cc=lehoangnamtep@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--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