From: Paul Louvel <paul.louvel@bootlin.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
David Howells <dhowells@redhat.com>
Cc: Paul Louvel <paul.louvel@bootlin.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>
Subject: [PATCH 0/2] talitos SEC1 ahash 32k request limitation
Date: Mon, 30 Mar 2026 12:28:17 +0200 [thread overview]
Message-ID: <20260330102820.29914-1-paul.louvel@bootlin.com> (raw)
Hi,
The first patch fixes the ahash request size limitation of 32k in the
talitos driver. This limitation is due to the fact that the driver was
using a single descriptor for the whole request, which is not enough to
handle larger requests. A change in the crypto core introduced the
regression. The patches split the request into multiple descriptors if
needed, allowing to handle requests larger than 32k.
The second patch is just cosmetic changes in order to make the code more
readable and consistent with the fix.
Thank you,
Paul.
Paul Louvel (2):
crypto: talitos - fix SEC1 32k ahash request limitation
crypto: talitos - rename first/last to first_desc/last_desc
drivers/crypto/talitos.c | 254 +++++++++++++++++++++++++--------------
1 file changed, 166 insertions(+), 88 deletions(-)
--
Paul Louvel, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2026-03-30 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 10:28 Paul Louvel [this message]
2026-03-30 10:28 ` [PATCH 1/2] crypto: talitos - fix SEC1 32k ahash request limitation Paul Louvel
2026-03-30 10:28 ` [PATCH 2/2] crypto: talitos - rename first/last to first_desc/last_desc Paul Louvel
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=20260330102820.29914-1-paul.louvel@bootlin.com \
--to=paul.louvel@bootlin.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=herve.codina@bootlin.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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