From: kernel test robot <lkp@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: [tip:master 11/25] vmlinux.o: warning: objtool: fred_exc_machine_check+0x185: call to __kasan_check_read() leaves .noinstr.text section
Date: Thu, 6 Nov 2025 12:16:10 +0100 [thread overview]
Message-ID: <202511061245.gdMzEtVA-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
head: 8411fdb92360d0b4d3337492a25ee2de7fb6c425
commit: 8375dadb8d4c6de0dc916ea50b376d9d946ce544 [11/25] Merge branch into tip/master: 'perf/core'
config: x86_64-randconfig-2005-20250721 (https://download.01.org/0day-ci/archive/20251106/202511061245.gdMzEtVA-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251106/202511061245.gdMzEtVA-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/202511061245.gdMzEtVA-lkp@intel.com/
All warnings (new ones prefixed by >>):
vmlinux.o: warning: objtool: exc_debug_user+0x1c9: call to __kasan_check_read() leaves .noinstr.text section
vmlinux.o: warning: objtool: exc_int3+0x15e: call to __kasan_check_read() leaves .noinstr.text section
vmlinux.o: warning: objtool: noist_exc_machine_check+0x179: call to __kasan_check_read() leaves .noinstr.text section
>> vmlinux.o: warning: objtool: fred_exc_machine_check+0x185: call to __kasan_check_read() leaves .noinstr.text section
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-11-06 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 11:16 kernel test robot [this message]
2025-11-06 11:25 ` Peter Zijlstra
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=202511061245.gdMzEtVA-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®