From: Herbert Xu <herbert@gondor.apana.org.au>
To: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Cc: Eric Biggers <ebiggers@kernel.org>
Subject: [v2 PATCH 0/2] crypto: Use nth_page instead of doing it by hand
Date: Wed, 12 Mar 2025 12:29:55 +0800 [thread overview]
Message-ID: <cover.1741753576.git.herbert@gondor.apana.org.au> (raw)
v2 removes the krb5 patch and changes the code so that nth_page is
only called if HIGHMEM is enabled. Also switch to from page_address
to lowmem_page_address.
This patch series is based on top of:
https://patchwork.kernel.org/project/linux-crypto/patch/20250310172016.153423-1-ebiggers@kernel.org/
Curiously, the Crypto API scatterwalk incremented pages by hand
rather than using nth_page. Possibly because scatterwalk predates
nth_page (the following commit is from the history tree):
commit 3957f2b34960d85b63e814262a8be7d5ad91444d
Author: James Morris <jmorris@intercode.com.au>
Date: Sun Feb 2 07:35:32 2003 -0800
[CRYPTO]: in/out scatterlist support for ciphers.
Fix this by using nth_page.
Herbert Xu (2):
crypto: scatterwalk - Use nth_page instead of doing it by hand
crypto: hash - Use nth_page instead of doing it by hand
crypto/ahash.c | 42 +++++++++++++++++++++++-------------
include/crypto/scatterwalk.h | 21 +++++++++++-------
2 files changed, 40 insertions(+), 23 deletions(-)
--
2.39.5
next reply other threads:[~2025-03-12 4:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 4:29 Herbert Xu [this message]
2025-03-12 4:29 ` [v2 PATCH 1/2] crypto: scatterwalk - Use nth_page instead of doing it by hand Herbert Xu
2025-03-12 19:56 ` Eric Biggers
2025-03-13 1:43 ` Herbert Xu
2025-03-13 3:13 ` Eric Biggers
2025-03-12 4:30 ` [v2 PATCH 2/2] crypto: hash " Herbert Xu
2025-03-12 20:09 ` Eric Biggers
2025-03-13 2:36 ` Herbert Xu
2025-03-13 3:07 ` Eric Biggers
2025-03-13 4:04 ` 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.1741753576.git.herbert@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=ebiggers@kernel.org \
--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