From: "Chawdhry, Manorit" <m-chawdhry@ti.com>
To: Thorsten Blum <blum@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto: sa2ul - avoid rollback in sa_init_ctx_info()
Date: Wed, 4 Nov 2026 13:06:15 +0000 [thread overview]
Message-ID: <727fd6fb-844b-4229-86e5-f34a8b518413@ti.com> (raw)
In-Reply-To: <20261104082056.47165-2-blum@kernel.org>
Hi Thorsten,
On 11/4/2026 1:50 PM, Thorsten Blum wrote:
> Allocate the security context before reserving a security context ID to
> avoid the rollback on allocation failure. Remove the now-unused local
> error variable.
>
> Signed-off-by: Thorsten Blum <blum@kernel.org>
> ---
> drivers/crypto/sa2ul.c | 22 ++++++----------------
> 1 file changed, 6 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/crypto/sa2ul.c b/drivers/crypto/sa2ul.c
> index e026fc14a411..964ddadaa211 100644
> --- a/drivers/crypto/sa2ul.c
> +++ b/drivers/crypto/sa2ul.c
> @@ -748,7 +748,12 @@ static int sa_init_ctx_info(struct sa_ctx_info *ctx,
> struct sa_crypto_data *data)
> {
> unsigned long bn;
> - int err;
> +
> + ctx->sc = dma_pool_alloc(data->sc_pool, GFP_KERNEL, &ctx->sc_phys);
> + if (!ctx->sc) {
> + dev_err(&data->pdev->dev, "Failed to allocate SC memory\n");
> + return -ENOMEM;
> + }
I have been working on a cleanup and the following patch [0] would
actually defeat
the purpose of the patch you've posted, with the addition of the check,
we'd have to
rollback this dma alloc'ed pool instead which just reverses the order of
rollback and
nothing else.
Are you okay if we drop this patch ( given am not seeing any criticality
) or do you see
it still helping after the context of the patch I shared?
Regards,
Manorit
>
> spin_lock(&data->scid_lock);
> bn = find_first_zero_bit(data->ctx_bm, SA_MAX_NUM_CTX);
> @@ -758,22 +763,7 @@ static int sa_init_ctx_info(struct sa_ctx_info *ctx,
>
> ctx->sc_id = (u16)(data->sc_id_start + bn);
>
> - ctx->sc = dma_pool_alloc(data->sc_pool, GFP_KERNEL, &ctx->sc_phys);
> - if (!ctx->sc) {
> - dev_err(&data->pdev->dev, "Failed to allocate SC memory\n");
> - err = -ENOMEM;
> - goto scid_rollback;
> - }
> -
> return 0;
> -
> -scid_rollback:
> - spin_lock(&data->scid_lock);
> - __clear_bit(bn, data->ctx_bm);
> - data->sc_id--;
> - spin_unlock(&data->scid_lock);
> -
> - return err;
> }
>
> static void sa_cipher_cra_exit(struct crypto_skcipher *tfm)
[0]:
https://lore.kernel.org/linux-crypto/20261104-b4-upstream-sa2ul-cleanup-v2-21-15ab90b3f9c2@ti.com/
next prev parent reply other threads:[~2026-11-04 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 8:20 Thorsten Blum
2026-11-04 13:06 ` Chawdhry, Manorit [this message]
2026-11-04 13:23 ` Thorsten Blum
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=727fd6fb-844b-4229-86e5-f34a8b518413@ti.com \
--to=m-chawdhry@ti.com \
--cc=blum@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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®