From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: arch/loongarch/kernel/traps.o: warning: objtool: do_lasx+0x134: unreachable instruction
Date: Sun, 11 Jan 2026 21:01:21 +0800 [thread overview]
Message-ID: <202601112003.IaGFdU88-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "loongarch: unreachable instruction"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Peter Zijlstra <peterz@infradead.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 755bc1335e3b116b702205b72eb57b7b8aef2bb2
commit: 06e24745985c8dd0da18337503afcf2f2fdbdff1 objtool: Remove annotate_{,un}reachable()
date: 1 year, 1 month ago
:::::: branch date: 11 hours ago
:::::: commit date: 1 year, 1 month ago
config: loongarch-randconfig-r053-20260108 (https://download.01.org/0day-ci/archive/20260111/202601112003.IaGFdU88-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260111/202601112003.IaGFdU88-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202601112003.IaGFdU88-lkp@intel.com/
All warnings (new ones prefixed by >>):
arch/loongarch/kernel/traps.o: warning: objtool: init_restore_lsx+0xcc: unreachable instruction
arch/loongarch/kernel/traps.o: warning: objtool: do_lbt+0x114: unreachable instruction
arch/loongarch/kernel/traps.o: warning: objtool: do_fpu+0x84: unreachable instruction
>> arch/loongarch/kernel/traps.o: warning: objtool: do_lasx+0x134: unreachable instruction
--
>> fs/crypto/keysetup.o: warning: objtool: fscrypt_setup_encryption_info+0x194: unreachable instruction
--
fs/btrfs/ctree.o: warning: objtool: insert_new_root+0xa4: unreachable instruction
fs/btrfs/ctree.o: warning: objtool: insert_ptr+0xa4: unreachable instruction
fs/btrfs/ctree.o: warning: objtool: copy_for_split+0x208: unreachable instruction
fs/btrfs/ctree.o: warning: objtool: btrfs_set_item_key_safe+0x2c8: unreachable instruction
fs/btrfs/ctree.o: warning: objtool: __push_leaf_left+0x458: unreachable instruction
fs/btrfs/ctree.o: warning: objtool: setup_items_for_insert.isra.0+0x148: unreachable instruction
fs/btrfs/ctree.o: warning: objtool: btrfs_truncate_item+0xe4: unreachable instruction
fs/btrfs/ctree.o: warning: objtool: btrfs_extend_item+0xb0: unreachable instruction
fs/btrfs/ctree.o: warning: objtool: balance_level+0xc28: unreachable instruction
>> fs/btrfs/ctree.o: warning: objtool: btrfs_search_slot+0x6c8: unreachable instruction
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-11 13:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202601112003.IaGFdU88-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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