From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: fs/btrfs/raid56.o: warning: objtool: raid56_parity_cache_data_folios+0x78: unreachable instruction
Date: Sun, 13 Sep 2026 07:07:38 +0800 [thread overview]
Message-ID: <202609130746.GuFroPOk-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: Qu Wenruo <wqu@suse.com>
CC: David Sterba <dsterba@suse.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: cba2348ab114391f5b1a00fa65c5b739f13f0563
commit: 5fbaae4b8567b19cd65b847043588e10af86eb60 btrfs: prepare scrub to support bs > ps cases
date: 12 months ago
:::::: branch date: 7 hours ago
:::::: commit date: 12 months ago
config: loongarch-randconfig-r061-20260906 (https://download.01.org/0day-ci/archive/20260913/202609130746.GuFroPOk-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/20260913/202609130746.GuFroPOk-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
| Fixes: 5fbaae4b8567 ("btrfs: prepare scrub to support bs > ps cases")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202609130746.GuFroPOk-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/btrfs/raid56.o: warning: objtool: raid_wait_read_end_io+0x74: unreachable instruction
fs/btrfs/raid56.o: warning: objtool: set_rbio_range_error+0x70: unreachable instruction
fs/btrfs/raid56.o: warning: objtool: alloc_rbio.isra.0+0x70: unreachable instruction
fs/btrfs/raid56.o: warning: objtool: rbio_add_io_sector+0xb8: unreachable instruction
fs/btrfs/raid56.o: warning: objtool: sector_in_rbio+0xd0: unreachable instruction
fs/btrfs/raid56.o: warning: objtool: rbio_stripe_sector+0x88: unreachable instruction
fs/btrfs/raid56.o: warning: objtool: assert_rbio+0x6c: unreachable instruction
fs/btrfs/raid56.o: warning: objtool: finish_parity_scrub+0x94: unreachable instruction
fs/btrfs/raid56.o: warning: objtool: rmw_assemble_write_bios.constprop.0+0x5c: unreachable instruction
fs/btrfs/raid56.o: warning: objtool: rmw_rbio+0x26c: unreachable instruction
fs/btrfs/raid56.o: warning: objtool: raid56_parity_recover+0x118: unreachable instruction
fs/btrfs/raid56.o: warning: objtool: raid56_parity_alloc_scrub_rbio+0x8c: unreachable instruction
>> fs/btrfs/raid56.o: warning: objtool: raid56_parity_cache_data_folios+0x78: unreachable instruction
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-12 23:07 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=202609130746.GuFroPOk-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