From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Josh Poimboeuf <jpoimboe@kernel•org>,
Peter Zijlstra <peterz@infradead•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: new objtool warnings
Date: Fri, 31 Oct 2025 11:15:15 +1100 [thread overview]
Message-ID: <20251031111515.09c9a4ed@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
Hi all,
My x86_64 allmodconfig builds started producing these warnings today:
vmlinux.o: warning: objtool: user_exc_vmm_communication+0x15a: call to __kasan_check_read() leaves .noinstr.text section
vmlinux.o: warning: objtool: exc_debug_user+0x182: call to __kasan_check_read() leaves .noinstr.text section
vmlinux.o: warning: objtool: exc_int3+0x123: call to __kasan_check_read() leaves .noinstr.text section
vmlinux.o: warning: objtool: noist_exc_machine_check+0x17a: call to __kasan_check_read() leaves .noinstr.text section
vmlinux.o: warning: objtool: fred_exc_machine_check+0x17e: call to __kasan_check_read() leaves .noinstr.text section
I can't easily tell what caused this change, sorry.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-10-31 0:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 0:15 Stephen Rothwell [this message]
2025-11-03 9:10 ` linux-next: new objtool warnings Peter Zijlstra
2025-11-03 9:32 ` Stephen Rothwell
2025-11-03 9:38 ` Peter Zijlstra
2025-11-05 3:30 ` Stephen Rothwell
2025-11-05 8:56 ` Peter Zijlstra
2025-11-05 10:00 ` Peter Zijlstra
2025-11-05 10:02 ` Peter Zijlstra
2025-11-05 10:10 ` Peter Zijlstra
2025-11-05 17:07 ` Nathan Chancellor
2025-11-05 19:16 ` Peter Zijlstra
2025-11-05 20:09 ` Nathan Chancellor
2025-11-06 11:48 ` 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=20251031111515.09c9a4ed@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jpoimboe@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=peterz@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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