From: Antoine Tenart <atenart@kernel.org>
To: Aleksander Jan Bajkowski <olek2@wp.pl>
Cc: ansuelsmth@gmail.com, atenart@kernel.org,
herbert@gondor.apana.org.au, davem@davemloft.net,
vschagen@icloud.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: inside-secure/eip93 - fix kernel panic in driver detach
Date: Mon, 5 Jan 2026 15:49:04 +0100 [thread overview]
Message-ID: <aVvPIJCy3rG2vL7Y@kwain> (raw)
In-Reply-To: <20251230211721.1110174-1-olek2@wp.pl>
On Tue, Dec 30, 2025 at 10:17:17PM +0100, Aleksander Jan Bajkowski wrote:
> During driver detach, the same hash algorithm is unregistered multiple
> times due to a wrong iterator.
>
> Fixes: 9739f5f93b78 ("crypto: eip93 - Add Inside Secure SafeXcel EIP-93 crypto engine support")
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
Reviewed-by: Antoine Tenart <atenart@kernel.org>
Thanks!
> ---
> drivers/crypto/inside-secure/eip93/eip93-main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/inside-secure/eip93/eip93-main.c b/drivers/crypto/inside-secure/eip93/eip93-main.c
> index 0b38a567da0e..3cdc3308dcac 100644
> --- a/drivers/crypto/inside-secure/eip93/eip93-main.c
> +++ b/drivers/crypto/inside-secure/eip93/eip93-main.c
> @@ -90,7 +90,7 @@ static void eip93_unregister_algs(unsigned int i)
> crypto_unregister_aead(&eip93_algs[j]->alg.aead);
> break;
> case EIP93_ALG_TYPE_HASH:
> - crypto_unregister_ahash(&eip93_algs[i]->alg.ahash);
> + crypto_unregister_ahash(&eip93_algs[j]->alg.ahash);
> break;
> }
> }
> --
> 2.47.3
>
next prev parent reply other threads:[~2026-01-05 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 21:17 [PATCH] crypto: inside-secure/eip93 - fix kernel panic in driver detach Aleksander Jan Bajkowski
2026-01-05 14:49 ` Antoine Tenart [this message]
2026-01-23 5:59 ` Herbert Xu
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=aVvPIJCy3rG2vL7Y@kwain \
--to=atenart@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=vschagen@icloud.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.