From: Jack Wang <jinpu.wang@ionos.com>
To: gregkh@linuxfoundation.org, sashal@kernel.org, stable@vger.kernel.org
Cc: dmitrii.omelchenko@cloud.ionos.com,
Jack Wang <jinpu.wang@cloud.ionos.com>
Subject: [PATCH 6.12.y 0/4] crypto: ccp, KVM: SVM - missing SEV/SNP platform-init dependency + 2 bugfixes
Date: Fri, 14 Aug 2026 12:02:53 +0200 [thread overview]
Message-ID: <20260814100652.225499-1-jinpu.wang@ionos.com> (raw)
From: Jack Wang <jinpu.wang@cloud.ionos.com>
Hello Greg, hello Sasha
Backport of 4 upstream commits to 6.12.y (applies on stable-rc
queue/6.12), Option 3 of stable-kernel-rules.rst (no Cc: stable tag
upstream).
Patches 1-2 are the missing dependencies of commit 3f8f0133a5fc
("crypto: ccp - Move SEV/SNP Platform initialization to KVM"), already
queued as of 6.12.97 (bb1c8464702540 on queue/6.12). That commit
dropped SEV/SNP platform init from the CCP driver's probe path,
expecting KVM to take over, but the counterpart commits that give KVM
that responsibility were never queued alongside it. Net effect:
6.12.97+ has no code path left that initializes SEV/SNP, so starting a
SEV-SNP guest crashes the host.
1) crypto: ccp - Add new SEV/SNP platform shutdown API
Upstream f7b86e0e75bc234751cb7a82d888083a57ef28b2
2) KVM: SVM: Add support to initialize SEV/SNP functionality in KVM
Upstream 6f1d5a3513c2370bbd6115dd430906bc2f4bdc53
Patches 3-4 are unrelated, independent bugfixes:
3) crypto: ccp - Fix checks for SNP_VLEK_LOAD input buffer length
Upstream ed53a5050f42a3243a7ed8dfa49030e54034b952
Context deviation: 6.12.y lacks the SEV_CMD_SNP_FEATURE_INFO case
the upstream hunk anchors on (added later, not queued here), so
the new case was placed after SEV_CMD_SNP_COMMIT instead. No
functional difference; noted as [Jack: ...] in the commit.
4) crypto: ccp - Abort doing SEV INIT if SNP INIT fails
Upstream 6131e119f5799bec55535530fa2fc44f5c7be1f1
Fixes SEV INIT succeeding to be issued (and failing) even when SNP
host support is enabled and SNP_INIT(_EX) hasn't succeeded.
Patches 1, 2 and 4 applied clean; only patch 3 needed the context
adjustment above. Please consider queue them for future release.
Thanks,
Jack Wang @ IONOS Cloud
Ashish Kalra (3):
crypto: ccp - Add new SEV/SNP platform shutdown API
KVM: SVM: Add support to initialize SEV/SNP functionality in KVM
crypto: ccp - Abort doing SEV INIT if SNP INIT fails
Michael Roth (1):
crypto: ccp - Fix checks for SNP_VLEK_LOAD input buffer length
arch/x86/kvm/svm/sev.c | 12 ++++++++++++
drivers/crypto/ccp/sev-dev.c | 17 ++++++++++++-----
include/linux/psp-sev.h | 3 +++
3 files changed, 27 insertions(+), 5 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-14 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 10:02 Jack Wang [this message]
2026-08-14 10:02 ` [stable-6.12 1/4] crypto: ccp - Add new SEV/SNP platform shutdown API Jack Wang
2026-08-14 10:02 ` [stable-6.12 2/4] KVM: SVM: Add support to initialize SEV/SNP functionality in KVM Jack Wang
2026-08-14 14:40 ` Sean Christopherson
2026-08-14 10:02 ` [stable-6.12 3/4] crypto: ccp - Fix checks for SNP_VLEK_LOAD input buffer length Jack Wang
2026-08-14 10:02 ` [stable-6.12 4/4] crypto: ccp - Abort doing SEV INIT if SNP INIT fails Jack Wang
2026-08-15 2:33 ` [PATCH 6.12.y 0/4] crypto: ccp, KVM: SVM - missing SEV/SNP platform-init dependency + 2 bugfixes Sasha Levin
2026-08-17 4:51 ` Jinpu Wang
2026-08-17 5:00 ` Greg KH
2026-08-17 5:22 ` Jinpu Wang
2026-08-17 5:34 ` Greg KH
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=20260814100652.225499-1-jinpu.wang@ionos.com \
--to=jinpu.wang@ionos.com \
--cc=dmitrii.omelchenko@cloud.ionos.com \
--cc=gregkh@linuxfoundation.org \
--cc=jinpu.wang@cloud.ionos.com \
--cc=sashal@kernel.org \
--cc=stable@vger.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