From: Eric Biggers via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: fsverity@lists.linux.dev
Cc: "Jason A . Donenfeld" <Jason@zx2c4.com>,
Theodore Ts'o <tytso@mit.edu>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Eric Biggers <ebiggers@kernel.org>,
linux-crypto@vger.kernel.org, linux-ext4@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>,
linux-btrfs@vger.kernel.org
Subject: [f2fs-dev] [PATCH 0/2] Convert fs/verity/ to use SHA-2 library API
Date: Mon, 30 Jun 2025 10:22:22 -0700 [thread overview]
Message-ID: <20250630172224.46909-1-ebiggers@kernel.org> (raw)
This series, including all its prerequisites, is also available at:
git fetch https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git fsverity-libcrypto-v1
This series makes fs/verity/ use the SHA-2 library API instead of the
old-school crypto API. This is simpler and more efficient.
This depends on my SHA-2 library improvements for 6.17 (many patches),
so this patchset might need to wait until 6.18. But I'm also thinking
about just basing the fsverity tree on libcrypto-next for 6.17.
Eric Biggers (2):
lib/crypto: hash_info: Move hash_info.c into lib/crypto/
fsverity: Switch from crypto_shash to SHA-2 library
Documentation/filesystems/fsverity.rst | 3 +-
crypto/Kconfig | 3 -
crypto/Makefile | 1 -
fs/verity/Kconfig | 6 +-
fs/verity/enable.c | 8 +-
fs/verity/fsverity_private.h | 24 +--
fs/verity/hash_algs.c | 194 +++++++++----------------
fs/verity/open.c | 36 ++---
fs/verity/verify.c | 7 +-
lib/crypto/Kconfig | 3 +
lib/crypto/Makefile | 2 +
{crypto => lib/crypto}/hash_info.c | 0
12 files changed, 107 insertions(+), 180 deletions(-)
rename {crypto => lib/crypto}/hash_info.c (100%)
--
2.50.0
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2025-06-30 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 17:22 Eric Biggers via Linux-f2fs-devel [this message]
2025-06-30 17:22 ` [f2fs-dev] [PATCH 1/2] lib/crypto: hash_info: Move hash_info.c into lib/crypto/ Eric Biggers via Linux-f2fs-devel
2025-06-30 17:22 ` [f2fs-dev] [PATCH 2/2] fsverity: Switch from crypto_shash to SHA-2 library Eric Biggers via Linux-f2fs-devel
2025-07-04 13:25 ` [f2fs-dev] [PATCH 0/2] Convert fs/verity/ to use SHA-2 library API Ard Biesheuvel via Linux-f2fs-devel
2025-07-09 19:26 ` Eric Biggers via Linux-f2fs-devel
2025-07-09 20:29 ` Eric Biggers via Linux-f2fs-devel
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=20250630172224.46909-1-ebiggers@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).