From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [zen:6.15/zen-sauce 6/30] fs/bcachefs/fsck.o: warning: objtool: check_key_has_inode+0x300: unreachable instruction
Date: Fri, 6 Jun 2025 20:53:07 +0800 [thread overview]
Message-ID: <202506062053.R9Be25rb-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "loongarch: unreachable instruction"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: steven@liquorix.net
tree: https://github.com/zen-kernel/zen-kernel 6.15/zen-sauce
head: 625fb48c0c4fab13b9c2f231c3fe6368a1b78242
commit: 490a2fd553b92e5ad5f151994a9bbf953cc000f7 [6/30] ZEN: Disable stack conservation for GCC
:::::: branch date: 12 hours ago
:::::: commit date: 12 hours ago
config: loongarch-randconfig-001-20250606 (https://download.01.org/0day-ci/archive/20250606/202506062053.R9Be25rb-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250606/202506062053.R9Be25rb-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/202506062053.R9Be25rb-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/bcachefs/fsck.o: warning: objtool: check_key_has_inode+0x300: unreachable instruction
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-06-06 12:53 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=202506062053.R9Be25rb-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.