[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251103203256.5ac39302@canb.auug.org.au>
Date: Mon, 3 Nov 2025 20:32:56 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Josh Poimboeuf <jpoimboe@...nel.org>, Linux Next Mailing List
<linux-next@...r.kernel.org>, Linux Kernel Mailing List
<linux-kernel@...r.kernel.org>
Subject: Re: linux-next: new objtool warnings
Hi Peter,
On Mon, 3 Nov 2025 10:10:06 +0100 Peter Zijlstra <peterz@...radead.org> wrote:
>
> On Fri, Oct 31, 2025 at 11:15:15AM +1100, Stephen Rothwell wrote:
> >
> > 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.
>
> What compiler? This smells like a broken compiler, these are all
> noinstr and that very much has __no_sanitize_address.
And today I didn't get them. So who knows? I did *not* change compiler
since Friday.
$ /usr/bin/x86_64-linux-gnu-gcc --version
x86_64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
Cross compiler hosted on ppc64 le.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists