From: Tom Lendacky <thomas.lendacky@amd.com>
To: Ashish Kalra <Ashish.Kalra@amd.com>,
john.allen@amd.com, herbert@gondor.apana.org.au,
davem@davemloft.net
Cc: aik@amd.com, dionnaglaze@google.com, michael.roth@amd.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] crypto: ccp: Fix SNP panic notifier unregistration
Date: Mon, 16 Jun 2025 15:46:49 -0500 [thread overview]
Message-ID: <9961dc02-3bab-3e68-47cd-93a5eb65e1ca@amd.com> (raw)
In-Reply-To: <20250605203803.4688-1-Ashish.Kalra@amd.com>
On 6/5/25 15:38, Ashish Kalra wrote:
> From: Ashish Kalra <ashish.kalra@amd.com>
>
> Panic notifiers are invoked with RCU read lock held and when the
> SNP panic notifier tries to unregister itself from the panic
> notifier callback itself it causes a deadlock as notifier
> unregistration does RCU synchronization.
>
> Code flow for SNP panic notifier:
> snp_shutdown_on_panic() ->
> __sev_firmware_shutdown() ->
> __sev_snp_shutdown_locked() ->
> atomic_notifier_chain_unregister(.., &snp_panic_notifier)
>
> Fix SNP panic notifier to unregister itself during SNP shutdown
> only if panic is not in progress.
>
> Fixes: 19860c3274fb ("crypto: ccp - Register SNP panic notifier only if SNP is enabled")
> Signed-off-by: Ashish Kalra <ashish.kalra@amd.com>
Looks good code-wise. A nice comment that explains the deadlock if
called during a panic would be good to add above the check for panic.
With that added:
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
> drivers/crypto/ccp/sev-dev.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/crypto/ccp/sev-dev.c b/drivers/crypto/ccp/sev-dev.c
> index 8fb94c5f006a..0ba5fe3b7883 100644
> --- a/drivers/crypto/ccp/sev-dev.c
> +++ b/drivers/crypto/ccp/sev-dev.c
> @@ -1787,8 +1787,9 @@ static int __sev_snp_shutdown_locked(int *error, bool panic)
> sev->snp_initialized = false;
> dev_dbg(sev->dev, "SEV-SNP firmware shutdown\n");
>
> - atomic_notifier_chain_unregister(&panic_notifier_list,
> - &snp_panic_notifier);
> + if (!panic)
> + atomic_notifier_chain_unregister(&panic_notifier_list,
> + &snp_panic_notifier);
>
> /* Reset TMR size back to default */
> sev_es_tmr_size = SEV_TMR_SIZE;
prev parent reply other threads:[~2025-06-16 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 20:38 [PATCH v2] crypto: ccp: Fix SNP panic notifier unregistration Ashish Kalra
2025-06-16 20:46 ` Tom Lendacky [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=9961dc02-3bab-3e68-47cd-93a5eb65e1ca@amd.com \
--to=thomas.lendacky@amd.com \
--cc=Ashish.Kalra@amd.com \
--cc=aik@amd.com \
--cc=davem@davemloft.net \
--cc=dionnaglaze@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
/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