From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: Yuwen Chen <ywen.chen@foxmail.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH 0/3] fscrypt: Switch to sync_skcipher and on-stack requests
Date: Tue, 8 Jul 2025 11:13:10 -0700 [thread overview]
Message-ID: <20250708181313.66961-1-ebiggers@kernel.org> (raw)
Simplify the code and eliminate per-encryption-op dynamic memory
allocations by switching from crypto_skcipher to crypto_sync_skcipher,
and from dynamic request allocation to SYNC_SKCIPHER_REQUEST_ON_STACK.
Previously, this change would have made the x86 accelerated AES code no
longer be used, which would have been very bad. However, I fixed that
in 6.16. So we can make this simplification now.
This patchset applies to fscrypt/for-next. The base-commit (listed
below) can be found in next-20250708
Eric Biggers (3):
fscrypt: Don't use asynchronous CryptoAPI algorithms
fscrypt: Drop FORBID_WEAK_KEYS flag for AES-ECB
fscrypt: Switch to sync_skcipher and on-stack requests
fs/crypto/crypto.c | 27 ++++++----------
fs/crypto/fname.c | 63 +++++++++++++------------------------
fs/crypto/fscrypt_private.h | 7 +++--
fs/crypto/keysetup.c | 23 +++++++-------
fs/crypto/keysetup_v1.c | 56 +++++++++++++++------------------
5 files changed, 71 insertions(+), 105 deletions(-)
base-commit: b41c1d8d07906786c60893980d52688f31d114a6
--
2.50.0
next reply other threads:[~2025-07-08 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 18:13 Eric Biggers [this message]
2025-07-08 18:13 ` [PATCH 1/3] fscrypt: Don't use asynchronous CryptoAPI algorithms Eric Biggers
2025-07-08 18:13 ` [PATCH 2/3] fscrypt: Drop FORBID_WEAK_KEYS flag for AES-ECB Eric Biggers
2025-07-08 18:13 ` [PATCH 3/3] fscrypt: Switch to sync_skcipher and on-stack requests Eric Biggers
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=20250708181313.66961-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ywen.chen@foxmail.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
all inboxes | Powered by JetHome®