From: Jihong Min <hurryman2212@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>,
Antoine Tenart <atenart@kernel.org>,
Christian Marangi <ansuelsmth@gmail.com>,
Richard van Schagen <vschagen@icloud.com>,
Benjamin Larsson <benjamin.larsson@genexis.eu>,
Mieczyslaw Nalewaj <namiltd@yahoo.com>,
Aleksander Jan Bajkowski <olek2@wp.pl>,
Jihong Min <hurryman2212@gmail.com>
Subject: [PATCH v2 0/5] crypto: eip93: fix request lifetime and completion handling
Date: Wed, 8 Jul 2026 02:15:32 +0900 [thread overview]
Message-ID: <20260707171537.467608-1-hurryman2212@gmail.com> (raw)
This is v2 of the EIP-93 fix series:
https://lore.kernel.org/linux-crypto/20260524194528.3666383-1-hurryman2212@gmail.com/
This series keeps the remaining request lifetime and completion handling
fixes from v1. Patch 1/6 from v1 is omitted because an equivalent
devm_request_threaded_irq() failure handling fix is already in this tree as
commit 85a61bf9145d ("crypto: inside-secure/eip93 - Add check for
devm_request_threaded_irq").
The patches collect EIP-93 fixes that had been carried out-of-tree and
rework them for the current driver. The original fixes came from work by
multiple people; the individual commits carry provenance trailers where the
original author, reporter or tester is known.
Tested on a Lumen W1700K2 wireless AP running a Linux 6.18 based OpenWrt
build, after verifying that the resulting driver changes match the
corresponding OpenWrt patch diffs, modulo upstream context differences.
Changes in v2:
- Drop the IRQ request error patch; the equivalent fix is already present.
- Rebase the remaining fixes onto cryptodev-2.6 master at e264401ce477.
- Keep the remaining code changes unchanged from v1.
Jihong Min (5):
crypto: eip93: guard DMA cleanup on uninitialized mappings
crypto: eip93: reject HMAC requests before setkey
crypto: eip93: use request-local SA records for cipher requests
crypto: eip93: order result descriptor reads after PE_READY
crypto: eip93: handle request ID exhaustion
.../crypto/inside-secure/eip93/eip93-aead.c | 34 +++++---
.../crypto/inside-secure/eip93/eip93-cipher.c | 34 +++++---
.../crypto/inside-secure/eip93/eip93-cipher.h | 3 +-
.../crypto/inside-secure/eip93/eip93-common.c | 65 ++++++++++++---
.../crypto/inside-secure/eip93/eip93-common.h | 3 +
.../crypto/inside-secure/eip93/eip93-hash.c | 79 +++++++++++++------
.../crypto/inside-secure/eip93/eip93-main.c | 19 +++--
.../crypto/inside-secure/eip93/eip93-main.h | 2 +
8 files changed, 174 insertions(+), 65 deletions(-)
base-commit: e264401ce4776a288524e5b87593d4d864147115
--
2.53.0
next reply other threads:[~2026-07-07 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 17:15 Jihong Min [this message]
2026-07-07 17:15 ` [PATCH v2 1/5] crypto: eip93: guard DMA cleanup on uninitialized mappings Jihong Min
2026-07-07 17:15 ` [PATCH v2 2/5] crypto: eip93: reject HMAC requests before setkey Jihong Min
2026-07-07 17:15 ` [PATCH v2 3/5] crypto: eip93: use request-local SA records for cipher requests Jihong Min
2026-07-07 17:15 ` [PATCH v2 4/5] crypto: eip93: order result descriptor reads after PE_READY Jihong Min
2026-07-07 17:15 ` [PATCH v2 5/5] crypto: eip93: handle request ID exhaustion 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=20260707171537.467608-1-hurryman2212@gmail.com \
--to=hurryman2212@gmail.com \
--cc=ansuelsmth@gmail.com \
--cc=atenart@kernel.org \
--cc=benjamin.larsson@genexis.eu \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namiltd@yahoo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox