mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Huacai Chen <chenhuacai@kernel.org>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] objtool/LoongArch: Fix fall through warning about efi_boot_kernel()
Date: Mon, 1 Sep 2025 10:16:16 +0200	[thread overview]
Message-ID: <20250901081616.GA4067720@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250901072156.31361-2-yangtiezhu@loongson.cn>

On Mon, Sep 01, 2025 at 03:21:54PM +0800, Tiezhu Yang wrote:
> When compiling with LLVM and CONFIG_LTO_CLANG is set, there exists
> the following objtool warning:
> 
>   vmlinux.o: warning: objtool: __efistub_efi_boot_kernel()
>   falls through to next function __efistub_exit_boot_func()
> 
> This is because efi_boot_kernel() doesn't end with a return instruction
> or an unconditional jump, then objtool has determined that the function
> can fall through into the next function.
> 
> At the beginning, try to do something to make efi_boot_kernel() ends with
> an unconditional jump instruction, but it is not a proper way.
> 
> After more analysis, one simple way is to ignore these EFISTUB functions
> in validate_branch() of objtool since they are useless for stack unwinder.
> 

This is drivers/firmware/efi/libstub/loongarch.c:efi_boot_kernel(),
right?

Why not simply do something like:

diff --git a/drivers/firmware/efi/libstub/loongarch.c b/drivers/firmware/efi/libstub/loongarch.c
index 3782d0a187d1..082611a5f1f0 100644
--- a/drivers/firmware/efi/libstub/loongarch.c
+++ b/drivers/firmware/efi/libstub/loongarch.c
@@ -81,4 +81,5 @@ efi_status_t efi_boot_kernel(void *handle, efi_loaded_image_t *image,
 
 	real_kernel_entry(true, (unsigned long)cmdline_ptr,
 			  (unsigned long)efi_system_table);
+	BUG();
 }

  reply	other threads:[~2025-09-01  8:16 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01  7:21 [PATCH v1 0/3] Fix objtool warnings if LTO is enabled for LoongArch (Part 2) Tiezhu Yang
2025-09-01  7:21 ` [PATCH v1 1/3] objtool/LoongArch: Fix fall through warning about efi_boot_kernel() Tiezhu Yang
2025-09-01  8:16   ` Peter Zijlstra [this message]
2025-09-01  8:31     ` Tiezhu Yang
2025-09-03 19:17       ` Josh Poimboeuf
2025-09-04  2:15         ` Tiezhu Yang
2025-09-04  2:17         ` Huacai Chen
2025-09-04 17:26           ` Josh Poimboeuf
2025-09-05  4:33             ` Huacai Chen
2025-09-05  9:53               ` Tiezhu Yang
2025-09-01  7:21 ` [PATCH v1 2/3] objtool/LoongArch: Fix unreachable instruction warnings about EFISTUB Tiezhu Yang
2025-09-01  8:19   ` Peter Zijlstra
2025-09-01  8:39     ` Tiezhu Yang
2025-09-03 19:19       ` Josh Poimboeuf
2025-09-04  2:18         ` Tiezhu Yang
2025-09-04  2:21           ` Huacai Chen
2025-09-04  3:50             ` Tiezhu Yang
2025-09-04  3:59               ` Huacai Chen
2025-09-04 17:39                 ` Josh Poimboeuf
2025-09-04 21:46                   ` Josh Poimboeuf
2025-09-05  4:36                     ` Huacai Chen
2025-09-05 16:04                       ` Josh Poimboeuf
2025-09-09  3:59                         ` Tiezhu Yang
2025-09-09  4:10                           ` Huacai Chen
2025-09-09 16:05                             ` Josh Poimboeuf
2025-09-10  6:55                               ` Huacai Chen
2025-09-11  3:23                                 ` Josh Poimboeuf
2025-09-11  8:28                                   ` Huacai Chen
2025-09-01  7:21 ` [PATCH v1 3/3] LoongArch: Fix unreachable instruction warnings about entry functions Tiezhu Yang
2025-09-01  8:20   ` Peter Zijlstra
2025-09-03 19:22   ` Josh Poimboeuf
2025-09-04  1:26     ` Jinyang He
2025-09-04  3:18     ` Tiezhu Yang
2025-09-04 17:16       ` Josh Poimboeuf
2025-09-02 15:43 ` [PATCH v1 0/3] Fix objtool warnings if LTO is enabled for LoongArch (Part 2) Huacai Chen

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=20250901081616.GA4067720@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=chenhuacai@kernel.org \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=yangtiezhu@loongson.cn \
    /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®