public inbox for linux-toolchains@vger.kernel.org
 help / color / mirror / Atom feed
From: Nam Le <lehoangnamtep@gmail.com>
To: Borislav Petkov <bp@alien8.de>,
	Segher Boessenkool <segher@kernel.crashing.org>
Cc: 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 13:01:24 +0100	[thread overview]
Message-ID: <2b848d54-c265-4675-91bd-a84fb2719b00@gmail.com> (raw)
In-Reply-To: <20260408100944.GBadYpaB8WLl78FamY@fat_crate.local>



On 08/04/2026 11:09, 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?
> 
> :-)
> 

I am not sure why ld.bfd doesn't add the section in, but it seems the LLVM
maintainers have no plans of making ld.lld behave the same as ld.bfd
according to the comments made here:

Link: https://github.com/llvm/llvm-project/issues/78873#issuecomment-1902794108 

> Sounds to me like you're shooting yourself in the foot on purpose:
> 
>        --dynamic-linker=value
>                Specify the dynamic linker to be used for a dynamically linked executable.
>                This is recorded in an ELF segment of type PT_INTERP.
> 
> So don't do that then.

Normally I would never add this flag, but some package manager
(specifically Nix) adds --dynamic-linker as a default when
building any applications. Ideally this should be a fix on LLVM's side
of things since its a pretty significant difference in behavior between
ld.lld and ld.bfd, but for the meantime I believe this is a minimal enough
change to fix the issue.

> 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.

Thank you for the advice! Should I add a comment and submit a v2 patch for the change?

  reply	other threads:[~2026-04-08 12:01 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 [this message]
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

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=2b848d54-c265-4675-91bd-a84fb2719b00@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