linux-kernel - Re: [PATCH v5 3/6] x86/sev: Split off startup code from core code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <C8291B70-FC38-43DF-B0DE-EF20DA769ABA@alien8.de>
Date: Thu, 24 Apr 2025 12:37:38 +0300
From: Borislav Petkov <bp@...en8.de>
To: Ard Biesheuvel <ardb@...nel.org>, Tom Lendacky <thomas.lendacky@....com>
CC: Ard Biesheuvel <ardb+git@...gle.com>, linux-kernel@...r.kernel.org,
 linux-efi@...r.kernel.org, x86@...nel.org, mingo@...nel.org,
 Dionna Amalie Glaze <dionnaglaze@...gle.com>,
 Kevin Loughlin <kevinloughlin@...gle.com>
Subject: Re: [PATCH v5 3/6] x86/sev: Split off startup code from core code

On April 23, 2025 6:50:00 PM GMT+03:00, Ard Biesheuvel <ardb@...nel.org> wrote:
>On Wed, 23 Apr 2025 at 17:22, Tom Lendacky <thomas.lendacky@....com> wrote:
>>
>> On 4/18/25 09:12, Ard Biesheuvel wrote:
>> > From: Ard Biesheuvel <ardb@...nel.org>
>> >
>> > Disentangle the SEV core code and the SEV code that is called during
>> > early boot. The latter piece will be moved into startup/ in a subsequent
>> > patch.
>> >
>> > Signed-off-by: Ard Biesheuvel <ardb@...nel.org>
>>
>> This patch breaks SNP guests. The SNP guest boots, but no longer has
>> access to the VMPCK keys needed to communicate with the ASP, which is
>> used, for example, to obtain an attestation report.
>>
>> It looks like the secrets_pa is defined as static in both startup.c and
>> core.c. It is set by a function in startup.c and so when used in core.c
>> its value will be 0.
>>
>> The following fixed the issue for me. Let me know if it can be squashed
>> in or a full patch is needed. Although, it likely should be named
>> sev_secrets_pa since it is no longer static.
>>
>
>Thanks for the fix, and apologies for using you as a guinea pig - I've
>been struggling to get access to SEV-SNP capable hardware, although a
>suitable EPYC based machine should be arriving in a month or 2.
>
>I'd assume a proper patch is better, and renaming it to sev_secrets_pa
>doesn't seem that intrusive. But it is ultimately Ingo's call.

Those patches should be applied *after* they have been tested. mingo knows that but does it anyway. :-(

This rushed patch application and hurried testing and sticking fixes ontop is completely counterproductive and annoying.

-- 
Sent from a small device: formatting sucks and brevity is inevitable.