linux-kernel - [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-next>] [day] [month] [year] [list]

Message-ID: <20250812132716.1465-1-yangtiezhu@loongson.cn>
Date: Tue, 12 Aug 2025 21:27:14 +0800
From: Tiezhu Yang <yangtiezhu@...ngson.cn>
To: Josh Poimboeuf <jpoimboe@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Huacai Chen <chenhuacai@...nel.org>,
	Nathan Chancellor <nathan@...nel.org>
Cc: loongarch@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] Fix objtool warnings if LTO is enabled for LoongArch

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.

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()

How to reproduce:

  $ make ARCH=loongarch LLVM=1 clean defconfig
  $ scripts/config -d LTO_NONE -e LTO_CLANG_THIN
  $ make ARCH=loongarch LLVM=1 olddefconfig all

Tiezhu Yang (2):
  objtool/LoongArch: Get table size correctly if LTO is enabled
  LoongArch: Pass annotate-tablejump option if LTO is enabled

 arch/loongarch/Makefile                |  6 ++++++
 tools/objtool/arch/loongarch/special.c | 23 +++++++++++++++++++++++
 2 files changed, 29 insertions(+)

-- 
2.42.0