From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: drivers/block/rbd.o: warning: objtool: rbd_img_handle_request+0xe0: unreachable instruction
Date: Sun, 6 Oct 2024 01:36:24 +0800 [thread overview]
Message-ID: <202410060153.ugFmLihV-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: Ilya Dryomov <idryomov@gmail.com>
CC: Dongsheng Yang <dongsheng.yang@easystack.cn>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 27cc6fdf720183dce1dbd293483ec5a9cb6b595e
commit: 2237ceb71f89837ac47c5dce2aaa2c2b3a337a3c rbd: don't assume RBD_LOCK_STATE_LOCKED for exclusive mappings
date: 2 months ago
:::::: branch date: 17 hours ago
:::::: commit date: 2 months ago
config: loongarch-randconfig-001-20240804 (https://download.01.org/0day-ci/archive/20241006/202410060153.ugFmLihV-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241006/202410060153.ugFmLihV-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/202410060153.ugFmLihV-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/block/rbd.o: warning: objtool: rbd_parse_param+0x2a0: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_quiesce_lock+0x6c: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_osd_setup_data+0xac: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_object_map_update_finish+0x90: unreachable instruction
drivers/block/rbd.o: warning: objtool: zero_bvecs+0x64: unreachable instruction
drivers/block/rbd.o: warning: objtool: set_bvec_pos+0x54: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_img_obj_request_del+0x44: unreachable instruction
drivers/block/rbd.o: warning: objtool: zero_bios+0x74: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_obj_advance_read+0x8c: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_dev_image_name+0x70: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_spec_fill_snap_id+0x60: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_spec_fill_names+0x5c: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_dev_header_info+0x64: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_dev_refresh+0xec: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_osd_setup_write_ops+0x170: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_obj_copyup_read_parent+0x54: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_obj_advance_copyup+0xe4: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_obj_advance_write+0xc0: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_img_advance+0xb0: unreachable instruction
>> drivers/block/rbd.o: warning: objtool: rbd_img_handle_request+0xe0: unreachable instruction
drivers/block/rbd.o: warning: objtool: wake_lock_waiters+0x98: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_acquire_lock+0x128: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_dev_image_probe+0x234: unreachable instruction
drivers/block/rbd.o: warning: objtool: do_rbd_add+0x4a8: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_slab_exit+0x2c: unreachable instruction
drivers/block/rbd.o: warning: objtool: rbd_init+0x78: unreachable instruction
objdump-func vmlinux.o rbd_img_handle_request:
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-10-05 17:37 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=202410060153.ugFmLihV-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.