From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: fs/btrfs/extent_io.o: warning: objtool: can_skip_one_ordered_range+0xe4: unreachable instruction
Date: Fri, 20 Mar 2026 08:24:54 +0800 [thread overview]
Message-ID: <202603200823.4JSF9ViZ-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>
CC: Filipe Manana <fdmanana@suse.com>
Hi Qu,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: a1d9d8e833781c44ab688708804ce35f20f3cbbd
commit: d2da21a6e06c40b9fd380ada93f1b48279e48b16 btrfs: introduce a read path dedicated extent lock helper
date: 1 year ago
:::::: branch date: 6 hours ago
:::::: commit date: 1 year ago
config: loongarch-randconfig-r053-20260318 (https://download.01.org/0day-ci/archive/20260320/202603200823.4JSF9ViZ-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260320/202603200823.4JSF9ViZ-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/202603200823.4JSF9ViZ-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/btrfs/extent_io.o: warning: objtool: can_skip_one_ordered_range+0xe4: unreachable instruction
fs/btrfs/extent_io.o: warning: objtool: set_delalloc_bitmap+0x100: unreachable instruction
fs/btrfs/extent_io.o: warning: objtool: assert_eb_folio_uptodate+0xc4: unreachable instruction
fs/btrfs/extent_io.o: warning: objtool: find_lock_delalloc_range+0x1d0: unreachable instruction
fs/btrfs/extent_io.o: warning: objtool: writepage_delalloc+0x410: unreachable instruction
fs/btrfs/extent_io.o: warning: objtool: attach_eb_folio_to_filemap+0x108: unreachable instruction
fs/btrfs/extent_io.o: warning: objtool: detach_extent_buffer_folio+0x10c: unreachable instruction
fs/btrfs/extent_io.o: warning: objtool: end_bbio_data_write+0x16c: unreachable instruction
fs/btrfs/extent_io.o: warning: objtool: submit_extent_folio+0xd8: unreachable instruction
fs/btrfs/extent_io.o: warning: objtool: submit_one_sector+0xcc: unreachable instruction
fs/btrfs/extent_io.o: warning: objtool: btrfs_do_readpage+0x204: unreachable instruction
fs/btrfs/extent_io.o: warning: objtool: extent_write_locked_range+0x220: unreachable instruction
fs/btrfs/extent_io.o: warning: objtool: alloc_extent_buffer+0x244: unreachable instruction
fs/btrfs/extent_io.o: warning: objtool: btrfs_clear_buffer_dirty+0x268: unreachable instruction
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-20 0:26 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=202603200823.4JSF9ViZ-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