From: Herbert Xu <herbert@gondor.apana.org.au>
To: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: [PATCH 0/2] crypto: Make memcpy_sglist usable for Crypto API
Date: Sun, 27 Apr 2025 08:42:49 +0800 [thread overview]
Message-ID: <cover.1745714222.git.herbert@gondor.apana.org.au> (raw)
I added memcpy_sglist for the simple SG lists used by zswap. It is
quite similar in terms functionality to the skcipher_null algorithm.
However, before memcpy_sglist can replace skcipher_null, it needs
to handle funky SG lists generated by IPsec. The SG lists are
distinct, but contain identical subsets.
This patch series adds this functionality to memcpy_sglist by
remodelling it on top of skcipher_walk instead of scatterwalk.
As a prerequisite, skcipher_walk has been abstracted out of skcipher
and moved into scatterwalk.
Herbert Xu (2):
crypto: ccp - Include crypto/utils.h for crypto_memneq
crypto: scatterwalk - Move skcipher walk and use it for memcpy_sglist
crypto/scatterwalk.c | 274 +++++++++++++++++++++++++++--
crypto/skcipher.c | 261 +--------------------------
drivers/crypto/ccp/ccp-ops.c | 11 +-
include/crypto/algapi.h | 12 --
include/crypto/internal/skcipher.h | 48 +----
include/crypto/scatterwalk.h | 65 ++++++-
6 files changed, 335 insertions(+), 336 deletions(-)
base-commit: 432f98cf56cf1e0f812f79a713847b37ae86cf31
--
2.39.5
next reply other threads:[~2025-04-27 0:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 0:42 Herbert Xu [this message]
2025-04-27 0:42 ` [PATCH 1/2] crypto: ccp - Include crypto/utils.h for crypto_memneq Herbert Xu
2025-04-27 0:42 ` [PATCH 2/2] crypto: scatterwalk - Move skcipher walk and use it for memcpy_sglist Herbert Xu
2025-04-27 1:08 ` Eric Biggers
2025-04-27 1:12 ` 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=cover.1745714222.git.herbert@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@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