[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bc84e6bf-594d-45c6-97a9-c5701412e345@infradead.org>
Date: Mon, 7 Jul 2025 22:44:30 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Josh Poimboeuf <jpoimboe@...nel.org>, Peter Zijlstra <peterz@...radead.org>,
Borislav Petkov <bp@...en8.de>, Joerg Roedel <jroedel@...e.de>
Subject: Re: linux-next: Tree for Jun 13 (objtool: __sev_es_nmi_complete+0x58)
(& July 02)
On 7/7/25 10:34 PM, Ard Biesheuvel wrote:
> On Thu, 3 Jul 2025 at 13:06, Randy Dunlap <rdunlap@...radead.org> wrote:
>>
>>
>>
>> On 6/13/25 7:59 PM, Randy Dunlap wrote:
>>>
>>>
>>> On 6/12/25 10:42 PM, Stephen Rothwell wrote:
>>>> Hi all,
>>>>
>>>> Changes since 20250612:
>>>>
>>>
>>> on x86_64:
>>>
>>> vmlinux.o: error: objtool: __sev_es_nmi_complete+0x58: call to __kcsan_check_access() leaves .noinstr.text section
>>>
>>>
>>> Full randconfig file is attached.
>>>
>>
>> I am still seeing this on linux-next 20250702.
>>
>> Adding BP, Joerg, Ard to Cc: list.
>>
>
> Where is this full randconfig that provokes it?
It's an attachment in the previous Jun 13 email. That email is here:
https://lore.kernel.org/linux-next/12838efb-238f-4bdd-af81-06c6408cee4f@infradead.org/
And I might as well provide here (attached) for you.
--
~Randy
Download attachment "config-r9540.gz" of type "application/gzip" (32589 bytes)
Powered by blists - more mailing lists