From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: drivers/md/dm-integrity.o: warning: objtool: sg_assign_page+0x20: unreachable instruction
Date: Thu, 20 Nov 2025 00:43:48 +0800 [thread overview]
Message-ID: <202511200025.BiqrEok0-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: Mikulas Patocka <mpatocka@redhat.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 8b690556d8fe074b4f9835075050fba3fb180e93
commit: 5076d4599ce1702ab3615c7600504ba68df02168 dm-integrity: enable asynchronous hash interface
date: 8 weeks ago
:::::: branch date: 23 hours ago
:::::: commit date: 8 weeks ago
config: loongarch-randconfig-r071-20251118 (https://download.01.org/0day-ci/archive/20251120/202511200025.BiqrEok0-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/20251120/202511200025.BiqrEok0-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/202511200025.BiqrEok0-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/md/dm-integrity.o: warning: objtool: sg_assign_page+0x20: unreachable instruction
drivers/md/dm-integrity.o: warning: objtool: do_journal_write+0x44c: unreachable instruction
drivers/md/dm-integrity.o: warning: objtool: dm_integrity_map_continue+0x45c: unreachable instruction
drivers/md/dm-integrity.o: warning: objtool: dm_integrity_dtr+0x34: unreachable instruction
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-19 16:44 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=202511200025.BiqrEok0-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.