From: Aleksander Jan Bajkowski <olek2@wp.pl>
To: Jihong Min <hurryman2212@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org
Cc: Christian Marangi <ansuelsmth@gmail.com>,
Antoine Tenart <atenart@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Richard van Schagen <vschagen@icloud.com>,
linux-kernel@vger.kernel.org,
Benjamin Larsson <benjamin.larsson@genexis.eu>,
Mieczyslaw Nalewaj <namiltd@yahoo.com>
Subject: Re: [PATCH 1/6] crypto: eip93: return IRQ request errors from probe
Date: Sun, 24 May 2026 23:09:50 +0200 [thread overview]
Message-ID: <ddb3ad67-5125-457a-b033-8804f08b4439@wp.pl> (raw)
In-Reply-To: <20260524194528.3666383-2-hurryman2212@gmail.com>
Hi Jihjong,
I sent same patch a few days ago. You can find it on Patchwork[1].
1.
https://patchwork.kernel.org/project/linux-crypto/patch/20260518212506.292170-1-olek2@wp.pl/
Best regards,
Aleksander
On 24/05/2026 21:45, Jihong Min wrote:
> devm_request_threaded_irq() can fail, but eip93_crypto_probe()
> continues as if the interrupt handler was installed. Return the error
> immediately so the driver does not register algorithms for a device that
> cannot signal completions.
>
> Fixes: 9739f5f93b78 ("crypto: eip93 - Add Inside Secure SafeXcel EIP-93 crypto engine support")
> Originally-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
> Assisted-by: Codex:gpt-5.5
> Signed-off-by: Jihong Min <hurryman2212@gmail.com>
> ---
> drivers/crypto/inside-secure/eip93/eip93-main.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/crypto/inside-secure/eip93/eip93-main.c b/drivers/crypto/inside-secure/eip93/eip93-main.c
> index 7dccfdeb7b11..276839e1a515 100644
> --- a/drivers/crypto/inside-secure/eip93/eip93-main.c
> +++ b/drivers/crypto/inside-secure/eip93/eip93-main.c
> @@ -433,6 +433,8 @@ static int eip93_crypto_probe(struct platform_device *pdev)
> ret = devm_request_threaded_irq(eip93->dev, eip93->irq, eip93_irq_handler,
> NULL, IRQF_ONESHOT,
> dev_name(eip93->dev), eip93);
> + if (ret)
> + return ret;
>
> eip93->ring = devm_kcalloc(eip93->dev, 1, sizeof(*eip93->ring), GFP_KERNEL);
> if (!eip93->ring)
next prev parent reply other threads:[~2026-05-24 21:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 19:45 [PATCH 0/6] crypto: eip93: fix request lifetime and completion handling Jihong Min
2026-05-24 19:45 ` [PATCH 1/6] crypto: eip93: return IRQ request errors from probe Jihong Min
2026-05-24 21:09 ` Aleksander Jan Bajkowski [this message]
2026-05-24 21:49 ` Jihong Min
2026-05-24 19:45 ` [PATCH 2/6] crypto: eip93: guard DMA cleanup on uninitialized mappings Jihong Min
2026-05-24 19:45 ` [PATCH 3/6] crypto: eip93: reject HMAC requests before setkey Jihong Min
2026-05-24 19:45 ` [PATCH 4/6] crypto: eip93: use request-local SA records for cipher requests Jihong Min
2026-05-24 19:45 ` [PATCH 5/6] crypto: eip93: order result descriptor reads after PE_READY Jihong Min
2026-05-24 19:45 ` [PATCH 6/6] crypto: eip93: handle request ID exhaustion Jihong Min
[not found] ` <e2242046-f08c-4903-a2ea-f21d3bb241cd@wp.pl>
2026-05-24 21:47 ` Jihong Min
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=ddb3ad67-5125-457a-b033-8804f08b4439@wp.pl \
--to=olek2@wp.pl \
--cc=ansuelsmth@gmail.com \
--cc=atenart@kernel.org \
--cc=benjamin.larsson@genexis.eu \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hurryman2212@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namiltd@yahoo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox