From: Mario Limonciello <superm1@kernel.org>
To: "Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Thomas, Rijo-john" <Rijo-john.Thomas@amd.com>
Cc: "Allen, John" <John.Allen@amd.com>,
"David S . Miller" <davem@davemloft.net>,
Hans de Goede <hansg@kernel.org>,
"open list:AMD CRYPTOGRAPHIC COPROCESSOR (CCP) DRIVER"
<linux-crypto@vger.kernel.org>,
"open list:AMD PMF DRIVER" <platform-driver-x86@vger.kernel.org>,
Lars Francke <lars.francke@gmail.com>,
Yijun Shen <Yijun.Shen@dell.com>
Subject: Re: [PATCH v4 5/5] crypto: ccp - Send PSP_CMD_TEE_RING_DESTROY when PSP_CMD_TEE_RING_INIT fails
Date: Sat, 10 Jan 2026 15:34:05 -0600 [thread overview]
Message-ID: <a8dcc943-3a96-4654-97a3-0adf55f6d4e1@kernel.org> (raw)
In-Reply-To: <f1cb81b7-5aab-48d0-99ce-5f971f5d2fa7@amd.com>
On 1/7/26 3:04 AM, Shyam Sundar S K wrote:
>
>
> On 1/6/2026 10:24, Mario Limonciello (AMD) wrote:
>> The hibernate resume sequence involves loading a resume kernel that is just
>> used for loading the hibernate image before shifting back to the existing
>> kernel.
>>
>> During that hibernate resume sequence the resume kernel may have loaded
>> the ccp driver. If this happens the resume kernel will also have called
>> PSP_CMD_TEE_RING_INIT but it will never have called
>> PSP_CMD_TEE_RING_DESTROY.
>>
>> This is problematic because the existing kernel needs to re-initialize the
>> ring. One could argue that the existing kernel should call destroy
>> as part of restore() but there is no guarantee that the resume kernel did
>> or didn't load the ccp driver. There is also no callback opportunity for
>> the resume kernel to destroy before handing back control to the existing
>> kernel.
>>
>> Similar problems could potentially exist with the use of kdump and
>> crash handling. I actually reproduced this issue like this:
>>
>> 1) rmmod ccp
>> 2) hibernate the system
>> 3) resume the system
>> 4) modprobe ccp
>>
>> The resume kernel will have loaded ccp but never destroyed and then when
>> I try to modprobe it fails.
>>
>> Because of these possible cases add a flow that checks the error code from
>> the PSP_CMD_TEE_RING_INIT call and tries to call PSP_CMD_TEE_RING_DESTROY
>> if it failed. If this succeeds then call PSP_CMD_TEE_RING_INIT again.
>>
>> Fixes: f892a21f51162 ("crypto: ccp - use generic power management")
>> Reported-by: Lars Francke <lars.francke@gmail.com>
>> Closes: https://lore.kernel.org/platform-driver-x86/CAD-Ua_gfJnQSo8ucS_7ZwzuhoBRJ14zXP7s8b-zX3ZcxcyWePw@mail.gmail.com/
>> Tested-by: Yijun Shen <Yijun.Shen@Dell.com>
>> Signed-off-by: Mario Limonciello (AMD) <superm1@kernel.org>
>> ---
>> v4:
>> * Add tag (Yijun)
>> * Move and rename PSP_TEE_STS_RING_BUSY (Ilpo)
>> v3:
>> * Add a comment (Tom)
>> * Add a define for busy condition (Shyam)
>> * Rename label (Shyam)
>> * Upgrade message to info (Shyam)
>> * Use a helper that validates result for destroy command (Shyam)
>> ---
>> drivers/crypto/ccp/tee-dev.c | 12 ++++++++++++
>> include/linux/psp.h | 1 +
>> 2 files changed, 13 insertions(+)
>>
>> diff --git a/drivers/crypto/ccp/tee-dev.c b/drivers/crypto/ccp/tee-dev.c
>> index ef1430f86ad62..ea9b94d5b10ba 100644
>> --- a/drivers/crypto/ccp/tee-dev.c
>> +++ b/drivers/crypto/ccp/tee-dev.c
>> @@ -113,6 +113,7 @@ static int tee_init_ring(struct psp_tee_device *tee)
>> {
>> int ring_size = MAX_RING_BUFFER_ENTRIES * sizeof(struct tee_ring_cmd);
>> struct tee_init_ring_cmd *cmd;
>> + bool retry = false;
>> unsigned int reg;
>> int ret;
>>
>> @@ -135,6 +136,7 @@ static int tee_init_ring(struct psp_tee_device *tee)
>> /* Send command buffer details to Trusted OS by writing to
>> * CPU-PSP message registers
>> */
>> +retry_init:
>> ret = psp_mailbox_command(tee->psp, PSP_CMD_TEE_RING_INIT, cmd,
>> TEE_DEFAULT_CMD_TIMEOUT, ®);
>> if (ret) {
>> @@ -145,6 +147,16 @@ static int tee_init_ring(struct psp_tee_device *tee)
>> }
>>
>> if (FIELD_GET(PSP_CMDRESP_STS, reg)) {
>> + /*
>> + * During the hibernate resume sequence driver may have gotten loaded
>> + * but the ring not properly destroyed. If the ring doesn't work, try
>> + * to destroy and re-init once.
>> + */
>> + if (!retry && FIELD_GET(PSP_CMDRESP_STS, reg) == PSP_TEE_STS_RING_BUSY) {
>> + dev_info(tee->dev, "tee: ring init command failed with busy status, retrying\n");
>> + if (tee_send_destroy_cmd(tee))
>
> so it becomes infinite retry? I think we need to set the retry flag to
> true to indicate that ring busy.
Great catch, thanks. I'll add the retry=true for this case.
>
>> + goto retry_init;
>> + }
>> dev_err(tee->dev, "tee: ring init command failed (%#010lx)\n",
>> FIELD_GET(PSP_CMDRESP_STS, reg));
>> tee_free_ring(tee);
>> diff --git a/include/linux/psp.h b/include/linux/psp.h
>> index 92e60aeef21e1..b337dcce1e991 100644
>> --- a/include/linux/psp.h
>> +++ b/include/linux/psp.h
>> @@ -18,6 +18,7 @@
>> * and should include an appropriate local definition in their source file.
>> */
>> #define PSP_CMDRESP_STS GENMASK(15, 0)
>> +#define PSP_TEE_STS_RING_BUSY 0x0000000d /* Ring already initialized */
>
> additional spaces between the macro names.
This was actually intended. I wanted to make it obvious that
PSP_TEE_STS_RING_BUSY reflects a value used for PSP_CMDRESP_STS.
>
> Thanks,
> Shyam
>
>> #define PSP_CMDRESP_CMD GENMASK(23, 16)
>> #define PSP_CMDRESP_RESERVED GENMASK(29, 24)
>> #define PSP_CMDRESP_RECOVERY BIT(30)
>
>
next prev parent reply other threads:[~2026-01-10 21:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 4:54 [PATCH v4 0/5] Fixes for PMF and CCP drivers after S4 Mario Limonciello (AMD)
2026-01-06 4:54 ` [PATCH v4 1/5] platform/x86/amd/pmf: Prevent TEE errors after hibernate Mario Limonciello (AMD)
2026-01-06 4:54 ` [PATCH v4 2/5] crypto: ccp - Declare PSP dead if PSP_CMD_TEE_RING_INIT fails Mario Limonciello (AMD)
2026-01-06 4:54 ` [PATCH v4 3/5] crypto: ccp - Add an S4 restore flow Mario Limonciello (AMD)
2026-01-06 13:42 ` kernel test robot
2026-01-07 7:59 ` Shyam Sundar S K
2026-01-06 4:54 ` [PATCH v4 4/5] crypto: ccp - Factor out ring destroy handling to a helper Mario Limonciello (AMD)
2026-01-06 4:54 ` [PATCH v4 5/5] crypto: ccp - Send PSP_CMD_TEE_RING_DESTROY when PSP_CMD_TEE_RING_INIT fails Mario Limonciello (AMD)
2026-01-07 9:04 ` Shyam Sundar S K
2026-01-10 21:34 ` Mario Limonciello [this message]
2026-01-07 14:06 ` [PATCH v4 0/5] Fixes for PMF and CCP drivers after S4 Tom Lendacky
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=a8dcc943-3a96-4654-97a3-0adf55f6d4e1@kernel.org \
--to=superm1@kernel.org \
--cc=John.Allen@amd.com \
--cc=Rijo-john.Thomas@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=Yijun.Shen@dell.com \
--cc=davem@davemloft.net \
--cc=hansg@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=lars.francke@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=platform-driver-x86@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