From: kernel test robot <lkp@intel.com>
To: Qu Wenruo <wqu@suse.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
David Sterba <dsterba@suse.com>
Subject: fs/btrfs/inode.o: warning: objtool: insert_inline_extent+0xa8: unreachable instruction
Date: Tue, 23 Jul 2024 13:32:02 +0800 [thread overview]
Message-ID: <202407231331.vNHHJPnu-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 66ebbdfdeb093e097399b1883390079cd4c3022b
commit: eb1fa9ab470285d39bee268bc2a90d1786610711 btrfs: make insert_inline_extent() accept one page directly
date: 3 months ago
config: loongarch-randconfig-001-20240722 (https://download.01.org/0day-ci/archive/20240723/202407231331.vNHHJPnu-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240723/202407231331.vNHHJPnu-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/oe-kbuild-all/202407231331.vNHHJPnu-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/btrfs/inode.o: warning: objtool: insert_inline_extent+0xa8: unreachable instruction
fs/btrfs/inode.o: warning: objtool: btrfs_del_delalloc_inode+0xb0: unreachable instruction
fs/btrfs/inode.o: warning: objtool: btrfs_set_delalloc_extent+0x18c: unreachable instruction
fs/btrfs/inode.o: warning: objtool: btrfs_evict_inode+0x9c: unreachable instruction
fs/btrfs/inode.o: warning: objtool: btrfs_get_extent+0x3d0: unreachable instruction
fs/btrfs/inode.o: warning: objtool: btrfs_set_range_writeback+0x7c: unreachable instruction
fs/btrfs/inode.o: warning: objtool: compress_file_range+0x388: unreachable instruction
fs/btrfs/inode.o: warning: objtool: cow_file_range+0x128: unreachable instruction
fs/btrfs/inode.o: warning: objtool: btrfs_finish_one_ordered+0x174: unreachable instruction
fs/btrfs/inode.o: warning: objtool: btrfs_invalidate_folio+0x1b8: unreachable instruction
objdump-func vmlinux.o insert_inline_extent:
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-07-23 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 5:32 kernel test robot [this message]
2024-07-23 5:37 ` fs/btrfs/inode.o: warning: objtool: insert_inline_extent+0xa8: unreachable instruction Qu Wenruo
2024-07-24 2:06 ` Philip Li
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=202407231331.vNHHJPnu-lkp@intel.com \
--to=lkp@intel.com \
--cc=dsterba@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wqu@suse.com \
/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.