From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: mm/gup.o: warning: objtool: __get_user_pages+0x340: unreachable instruction
Date: Sun, 11 Jan 2026 11:17:53 +0800 [thread overview]
Message-ID: <202601111141.raJppYfV-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: Peter Zijlstra <peterz@infradead.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 97313d6113ab4362ad15076f65560e65288fbcb8
commit: 624bde3465f660e54a7cd4c1efc3e536349fead5 loongarch: Use ASM_REACHABLE
date: 1 year, 1 month ago
:::::: branch date: 10 hours ago
:::::: commit date: 1 year, 1 month ago
config: loongarch-randconfig-r053-20260108 (https://download.01.org/0day-ci/archive/20260111/202601111141.raJppYfV-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/20260111/202601111141.raJppYfV-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/202601111141.raJppYfV-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/gup.o: warning: objtool: __get_user_pages+0x340: unreachable instruction
mm/gup.o: warning: objtool: get_user_pages_remote+0x178: unreachable instruction
mm/gup.o: warning: objtool: get_user_pages+0x14c: unreachable instruction
mm/gup.o: warning: objtool: get_user_pages_unlocked+0x14c: unreachable instruction
mm/gup.o: warning: objtool: __gup_longterm_locked+0x12c: unreachable instruction
mm/gup.o: warning: objtool: faultin_page_range+0x120: unreachable instruction
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-11 3:18 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=202601111141.raJppYfV-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