From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: fsverity@lists.linux.dev, linux-crypto@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Theodore Ts'o <tytso@mit.edu>, Ard Biesheuvel <ardb@kernel.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [GIT PULL] Interleaved SHA-256 hashing support for 6.18
Date: Sat, 27 Sep 2025 13:24:10 -0700 [thread overview]
Message-ID: <20250927202410.GC9798@quark> (raw)
Note: this depends on the pull request
"[GIT PULL 03/12 for v6.18] inode" from Christian Brauner.
The following changes since commit f0883b9c395ecdf7e66a58b6027fd35056cf152c:
Merge patch series "Move fscrypt and fsverity info out of struct inode" (2025-08-21 13:58:13 +0200)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/fsverity/linux.git tags/fsverity-for-linus
for you to fetch changes up to a1f692fd69ccdbe1e492d366788b63227d429753:
fsverity: Use 2-way interleaved SHA-256 hashing when supported (2025-09-17 13:10:04 -0500)
----------------------------------------------------------------
Add support for 2-way interleaved SHA-256 hashing to lib/crypto/, and
make fsverity use it for faster file data verification. This improves
fsverity performance on many x86_64 and arm64 processors.
Later, I plan to make dm-verity use this too.
----------------------------------------------------------------
Eric Biggers (6):
lib/crypto: sha256: Add support for 2-way interleaved hashing
lib/crypto: arm64/sha256: Add support for 2-way interleaved hashing
lib/crypto: x86/sha256: Add support for 2-way interleaved hashing
lib/crypto: tests: Add tests and benchmark for sha256_finup_2x()
fsverity: Remove inode parameter from fsverity_hash_block()
fsverity: Use 2-way interleaved SHA-256 hashing when supported
fs/verity/enable.c | 12 +-
fs/verity/fsverity_private.h | 2 +-
fs/verity/hash_algs.c | 3 +-
fs/verity/verify.c | 175 +++++++++++++++----
include/crypto/sha2.h | 28 +++
lib/crypto/arm64/sha256-ce.S | 284 ++++++++++++++++++++++++++++++-
lib/crypto/arm64/sha256.h | 37 ++++
lib/crypto/sha256.c | 71 +++++++-
lib/crypto/tests/sha256_kunit.c | 184 ++++++++++++++++++++
lib/crypto/x86/sha256-ni-asm.S | 368 ++++++++++++++++++++++++++++++++++++++++
lib/crypto/x86/sha256.h | 39 +++++
11 files changed, 1147 insertions(+), 56 deletions(-)
next reply other threads:[~2025-09-27 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 20:24 Eric Biggers [this message]
2025-09-29 23:22 ` [GIT PULL] Interleaved SHA-256 hashing support for 6.18 pr-tracker-bot
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=20250927202410.GC9798@quark \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).