All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-kbuild@vger.kernel.org, Nicolas Schier <nsc@kernel.org>
Subject: Re: linux-next: new objtool warnings
Date: Wed, 5 Nov 2025 13:09:23 -0700	[thread overview]
Message-ID: <20251105200923.GA3787308@ax162> (raw)
In-Reply-To: <20251105191613.GA1831451@noisy.programming.kicks-ass.net>

On Wed, Nov 05, 2025 at 08:16:13PM +0100, Peter Zijlstra wrote:
> # make O=tmp-build clean
> # make O=tmp-build allmodconfig
> # make O=tmp-build -j64 vmlinux 2>&1 | grep "\[M\]"
>   CC [M]  sound/sound_core.o
>   CC [M]  virt/lib/irqbypass.o
>   AS [M]  arch/x86/crypto/twofish-x86_64-asm_64.o
>   CC [M]  arch/x86/crypto/twofish_glue.o
>   CC [M]  samples/vfio-mdev/mtty.o
>   CC [M]  sound/ac97_bus.o
>   AS [M]  arch/x86/crypto/twofish-x86_64-asm_64-3way.o
>   CC [M]  arch/x86/crypto/twofish_glue_3way.o

Thanks, I bisected this to commit d2d5cba5d92c ("kbuild: remove EXPERT
and !COMPILE_TEST guarding from TRIM_UNUSED_KSYMS"), which explains
everything when looking at Makefile:

  ifdef CONFIG_TRIM_UNUSED_KSYMS
  # For the kernel to actually contain only the needed exported symbols,
  # we have to build modules as well to determine what those symbols are.
  KBUILD_MODULES := y
  endif

Maybe we want to restore the !COMPILE_TEST dependency?

Cheers,
Nathan

  reply	other threads:[~2025-11-05 20:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31  0:15 linux-next: new objtool warnings Stephen Rothwell
2025-11-03  9:10 ` Peter Zijlstra
2025-11-03  9:32   ` Stephen Rothwell
2025-11-03  9:38     ` Peter Zijlstra
2025-11-05  3:30       ` Stephen Rothwell
2025-11-05  8:56         ` Peter Zijlstra
2025-11-05 10:00           ` Peter Zijlstra
2025-11-05 10:02             ` Peter Zijlstra
2025-11-05 10:10               ` Peter Zijlstra
2025-11-05 17:07                 ` Nathan Chancellor
2025-11-05 19:16                   ` Peter Zijlstra
2025-11-05 20:09                     ` Nathan Chancellor [this message]
2025-11-06 11:48                       ` Peter Zijlstra
2025-11-05 13:00             ` [tip: perf/core] entry,unwind/deferred: Fix unwind_reset_info() placement tip-bot2 for Peter Zijlstra

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=20251105200923.GA3787308@ax162 \
    --to=nathan@kernel.org \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nsc@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.