[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220527044711.hrqxx5gz3jghydax@treble>
Date: Thu, 26 May 2022 21:47:11 -0700
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the tip tree with the kbuild tree
On Fri, May 27, 2022 at 11:19:02AM +0900, Masahiro Yamada wrote:
> [1] original behavior in Josh's commit
>
> $ git checkout 753da4179d08b625d8df72e97724e22749969fd3
> $ make defconfig
> $ make -j8 kernel/
> $ head -n 1 kernel/.fork.o.cmd
>
>
> I do not see the "--linked" parameter in the objtool command.
>
>
>
>
> [2] behavior in linux-next
>
>
> $ git checkout next-20220523
> $ make defconfig
> $ make -j8 kernel/
> $ head -n 1 kernel/.fork.o.cmd
>
> I see the "--linked" parameter in the objtool command.
>
> kernel/fork.o is a direct output from GCC,
> not from linker.
Yes, good catch. That flag should only be used for linked objects like
vmlinux.o or some_module.o.
Objtool only runs on such objects when CONFIG_LTO_CLANG,
CONFIG_X86_KERNEL_IBT, or CONFIG_NOINSTR_VALIDATION (vmlinux.o-only) is
enabled.
--
Josh
Powered by blists - more mailing lists