From: Tom Lendacky <thomas.lendacky@amd.com>
To: Runyu Xiao <runyu.xiao@seu.edu.cn>, mario.limonciello@amd.com
Cc: john.allen@amd.com, herbert@gondor.apana.org.au,
davem@davemloft.net, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
jianhao.xu@seu.edu.cn
Subject: Re: [PATCH v2] crypto: ccp: Initialize DBC ioctl mutex before registering device
Date: Sun, 30 Aug 2026 10:19:05 -0500 [thread overview]
Message-ID: <d1a21184-8b24-4612-bd4b-6cacf39962cf@amd.com> (raw)
In-Reply-To: <20260830015104.2040153-1-runyu.xiao@seu.edu.cn>
On 8/29/26 20:51, Runyu Xiao wrote:
> dbc_dev_init() registers the DBC misc device before initializing
> ioctl_mutex. Once misc_register() publishes the device, userspace can
> open it and invoke dbc_ioctl() while the mutex is still uninitialized.
>
> Initialize ioctl_mutex before calling misc_register() so the published
> ioctl callback always sees an initialized mutex.
>
> Fixes: c04cf9e14f10 ("crypto: ccp - Add support for fetching a nonce for dynamic boost control")
> Cc: stable@vger.kernel.org
> Link: https://lore.kernel.org/all/20260829133410.1708684-1-runyu.xiao@seu.edu.cn/
> Signed-off-by: Runyu Xiao <runyu.xiao@seu.edu.cn>
> Assisted-by: Codex:GPT-5
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
> v2:
> - Move mutex initialization before setting up the misc device, as suggested
> by Tom Lendacky.
>
> drivers/crypto/ccp/dbc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/crypto/ccp/dbc.c b/drivers/crypto/ccp/dbc.c
> index 410084a9039c..4db49a14550c 100644
> --- a/drivers/crypto/ccp/dbc.c
> +++ b/drivers/crypto/ccp/dbc.c
> @@ -235,6 +235,8 @@ int dbc_dev_init(struct psp_device *psp)
> goto cleanup_mbox;
> }
>
> + mutex_init(&dbc_dev->ioctl_mutex);
> +
> dbc_dev->char_dev.minor = MISC_DYNAMIC_MINOR;
> dbc_dev->char_dev.name = "dbc";
> dbc_dev->char_dev.fops = &dbc_fops;
> @@ -243,8 +245,6 @@ int dbc_dev_init(struct psp_device *psp)
> if (ret)
> goto cleanup_mbox;
>
> - mutex_init(&dbc_dev->ioctl_mutex);
> -
> return 0;
>
> cleanup_mbox:
prev parent reply other threads:[~2026-08-30 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 13:34 [PATCH] " Runyu Xiao
2026-08-29 15:07 ` Tom Lendacky
2026-08-30 1:51 ` [PATCH v2] " Runyu Xiao
2026-08-30 15:19 ` 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=d1a21184-8b24-4612-bd4b-6cacf39962cf@amd.com \
--to=thomas.lendacky@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jianhao.xu@seu.edu.cn \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=runyu.xiao@seu.edu.cn \
--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
all inboxes | Powered by JetHome®