From: Randy Dunlap <rdunlap@infradead.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@alien8.de>, Joerg Roedel <jroedel@suse.de>
Subject: Re: linux-next: Tree for Jun 13 (objtool: __sev_es_nmi_complete+0x58) (& July 02)
Date: Mon, 7 Jul 2025 22:44:30 -0700 [thread overview]
Message-ID: <bc84e6bf-594d-45c6-97a9-c5701412e345@infradead.org> (raw)
In-Reply-To: <CAMj1kXGDiCAkHYi6YY2Tq87Le4Ry=pBbaVWSk_wPzNsj8kcXtA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
On 7/7/25 10:34 PM, Ard Biesheuvel wrote:
> On Thu, 3 Jul 2025 at 13:06, Randy Dunlap <rdunlap@infradead.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
[-- Attachment #2: config-r9540.gz --]
[-- Type: application/gzip, Size: 32589 bytes --]
next prev parent reply other threads:[~2025-07-08 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 5:42 linux-next: Tree for Jun 13 Stephen Rothwell
2025-06-14 2:59 ` linux-next: Tree for Jun 13 (objtool: __sev_es_nmi_complete+0x58) Randy Dunlap
2025-07-03 3:06 ` linux-next: Tree for Jun 13 (objtool: __sev_es_nmi_complete+0x58) (& July 02) Randy Dunlap
2025-07-08 5:34 ` Ard Biesheuvel
2025-07-08 5:44 ` Randy Dunlap [this message]
2025-06-14 3:10 ` linux-next: Tree for Jun 13 (drivers/gpu/drm/i915/display/intel_backlight.c) Randy Dunlap
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=bc84e6bf-594d-45c6-97a9-c5701412e345@infradead.org \
--to=rdunlap@infradead.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=jpoimboe@kernel.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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®