linux-kernel - Re: [PATCH 0/2] Fix objtool warnings if LTO is enabled for LoongArch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAAhV-H4pYKb9+XUZW4QNWiMQSZVBBsVSvDNB5RvKWnxFEC-gcg@mail.gmail.com>
Date: Sat, 16 Aug 2025 22:59:47 +0800
From: Huacai Chen <chenhuacai@...nel.org>
To: Nathan Chancellor <nathan@...nel.org>
Cc: Tiezhu Yang <yangtiezhu@...ngson.cn>, Josh Poimboeuf <jpoimboe@...nel.org>, 
	Peter Zijlstra <peterz@...radead.org>, loongarch@...ts.linux.dev, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Fix objtool warnings if LTO is enabled for LoongArch

On Fri, Aug 15, 2025 at 7:01 AM Nathan Chancellor <nathan@...nel.org> wrote:
>
> On Tue, Aug 12, 2025 at 09:27:14PM +0800, Tiezhu Yang wrote:
> > The patch #1 should be a preparation for patch #2, that is to say,
> > the patch #2 is dependent on the patch #1, otherwise there is build
> > error if LTO is enabled after only applying patch #2.
>
> Thanks, these two patches do indeed resolve most of the warnings that I
> see.
>
> Tested-by: Nathan Chancellor <nathan@...nel.org>
>
> > With this series, most of warnings have been silenced, only remains
> > the following warning by now, it needs more analysis:
> >
> >   vmlinux.o: warning: objtool: __efistub_efi_boot_kernel() falls through
> >   to next function __efistub_exit_boot_func()
>
> Yes, I do see this one too. Odd, as efi_boot_kernel() ends in a
> __noreturn function...
But this one only exists for LTO?

Huacai

>
> Cheers,
> Nathan