mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Mathias Krause <minipli@grsecurity.net>
Cc: Nicolas Schier <nsc@kernel.org>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: prevent building single targets twice
Date: Thu, 22 Oct 2026 12:37:11 -0700	[thread overview]
Message-ID: <20261022193711.GB3692072@ax162> (raw)
In-Reply-To: <e313803a-47ba-4d27-89d9-47dd1abb5183@grsecurity.net>

On Thu, Oct 22, 2026 at 12:05:27PM +0200, Mathias Krause wrote:
> Already visible in the diff context is 'libs-y' which has the same issue
> and a real behavioral change, depending on which compiler invocation
> runs last for arch/x86/lib/delay.o, it'll either be compiled with or
> without -pg under KCSAN.

Ah, I had not realized that libs-y suffered from the same problem.

> Others are:
> - arch/x86/platform/pvh/enlighten.o (via arch/x86/Kbuild),
> - drivers/char/ipmi/ipmi_msghandler.o (via drivers/Makefile,
>   intentionally there for init ordering),
> - drivers/input/serio/i8042.o (also via drivers/Makefile)
> 
> But what's worse, your change also affects link order which also defines
> runtime initialization order. I don't want to crawl into that rabbit
> hole and look for all the implicit dependencies that'd be broken by that
> change...
> 
> One obvious, however, would be pci_subsys_init() which would then run
> before acpi_init(), leaving out ACPI-discovered PCI roots from getting
> discovered.
> 
> So no, I don't like your change and prefer the more fundamental kbuild
> fix to get this sorted out once for all.

Totally fair, I had briefly thought about that but did not fully
consider all implications, so thanks for pointing that out.

I'll keep your change in my review queue and study it soon.

-- 
Cheers,
Nathan

      reply	other threads:[~2026-10-22 19:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 12:39 Mathias Krause
2026-10-21  6:53 ` Mathias Krause
2026-10-21 17:04   ` Nicolas Schier
2026-10-21 19:03     ` Nathan Chancellor
2026-10-21 21:25       ` Mathias Krause
2026-10-21 21:55         ` Nathan Chancellor
2026-10-22 10:05           ` Mathias Krause
2026-10-22 19:37             ` Nathan Chancellor [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=20261022193711.GB3692072@ax162 \
    --to=nathan@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minipli@grsecurity.net \
    --cc=nsc@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

all inboxes | Powered by JetHome®