From: Herbert Xu <herbert@gondor.apana.org.au>
To: Tycho Andersen <tycho@kernel.org>
Cc: Ashish Kalra <ashish.kalra@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] crypto: ccp - Bump minimum firmware version for SEV-SNP support
Date: Fri, 13 Nov 2026 21:06:52 +0800 [thread overview]
Message-ID: <avcLbMdvNaIuzfW8@gondor.apana.org.au> (raw)
In-Reply-To: <20261103181002.2200214-1-tycho@kernel.org>
On Tue, Nov 03, 2026 at 11:10:01AM -0700, Tycho Andersen wrote:
> From: "Tycho Andersen (AMD)" <tycho@kernel.org>
>
> The SEV firmware has received many critical bug and security fixes since
> 1.52. Bump the minimum supported firmware version for SEV-SNP to 1.55
> (first available in linux-firmware release 20230919). See
> https://www.amd.com/en/developer/sev.html for firmware release notes with
> exact bug fixes and CVE details.
>
> While these macros are called SNP_MIN_API_*, since 6131e119f579 ("crypto:
> ccp - Abort doing SEV INIT if SNP INIT fails") both SEV and SNP fail if SNP
> fails to initialize, so this firmware requirement really applies to SEV
> hosts that are SNP capable at the time of init.
>
> Also upgrade the debug log to an error log to give people some idea about
> why things failed.
>
> Signed-off-by: Tycho Andersen (AMD) <tycho@kernel.org>
> Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
> drivers/crypto/ccp/sev-dev.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
All applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2026-11-13 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 18:10 Tycho Andersen
2026-11-03 18:10 ` [PATCH v1 2/2] crypto: ccp - Drop support for SNP without INIT_EX Tycho Andersen
2026-11-13 13:06 ` Herbert Xu [this message]
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=avcLbMdvNaIuzfW8@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=ashish.kalra@amd.com \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=tycho@kernel.org \
/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®