From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, Yuwen Chen <ywen.chen@foxmail.com>,
linux-mtd@lists.infradead.org, ceph-devel@vger.kernel.org,
linux-kernel@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH v2 0/6] fscrypt: Switch to sync_skcipher and on-stack requests
Date: Wed, 9 Jul 2025 23:07:47 -0700 [thread overview]
Message-ID: <20250710060754.637098-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
Changed in v2:
- Added patches that remove the gfp_t argument from functions that no
longer need it.
- Eliminated the goto in derive_key_aes().
- Improved commit messages.
Eric Biggers (6):
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
fscrypt: Remove gfp_t argument from fscrypt_crypt_data_unit()
fscrypt: Remove gfp_t argument from fscrypt_encrypt_block_inplace()
ceph: Remove gfp_t argument from ceph_fscrypt_encrypt_*()
fs/ceph/crypto.c | 13 +++-----
fs/ceph/crypto.h | 10 +++---
fs/ceph/file.c | 3 +-
fs/ceph/inode.c | 3 +-
fs/crypto/bio.c | 3 +-
fs/crypto/crypto.c | 44 +++++++++-----------------
fs/crypto/fname.c | 63 +++++++++++++------------------------
fs/crypto/fscrypt_private.h | 10 +++---
fs/crypto/keysetup.c | 23 +++++++-------
fs/crypto/keysetup_v1.c | 56 ++++++++++++++-------------------
fs/ubifs/crypto.c | 2 +-
include/linux/fscrypt.h | 5 ++-
12 files changed, 91 insertions(+), 144 deletions(-)
base-commit: b41c1d8d07906786c60893980d52688f31d114a6
--
2.50.1
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, Yuwen Chen <ywen.chen@foxmail.com>,
linux-mtd@lists.infradead.org, ceph-devel@vger.kernel.org,
linux-kernel@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH v2 0/6] fscrypt: Switch to sync_skcipher and on-stack requests
Date: Wed, 9 Jul 2025 23:07:47 -0700 [thread overview]
Message-ID: <20250710060754.637098-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
Changed in v2:
- Added patches that remove the gfp_t argument from functions that no
longer need it.
- Eliminated the goto in derive_key_aes().
- Improved commit messages.
Eric Biggers (6):
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
fscrypt: Remove gfp_t argument from fscrypt_crypt_data_unit()
fscrypt: Remove gfp_t argument from fscrypt_encrypt_block_inplace()
ceph: Remove gfp_t argument from ceph_fscrypt_encrypt_*()
fs/ceph/crypto.c | 13 +++-----
fs/ceph/crypto.h | 10 +++---
fs/ceph/file.c | 3 +-
fs/ceph/inode.c | 3 +-
fs/crypto/bio.c | 3 +-
fs/crypto/crypto.c | 44 +++++++++-----------------
fs/crypto/fname.c | 63 +++++++++++++------------------------
fs/crypto/fscrypt_private.h | 10 +++---
fs/crypto/keysetup.c | 23 +++++++-------
fs/crypto/keysetup_v1.c | 56 ++++++++++++++-------------------
fs/ubifs/crypto.c | 2 +-
include/linux/fscrypt.h | 5 ++-
12 files changed, 91 insertions(+), 144 deletions(-)
base-commit: b41c1d8d07906786c60893980d52688f31d114a6
--
2.50.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2025-07-10 6:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 6:07 Eric Biggers [this message]
2025-07-10 6:07 ` [PATCH v2 0/6] fscrypt: Switch to sync_skcipher and on-stack requests Eric Biggers
2025-07-10 6:07 ` [PATCH v2 1/6] fscrypt: Don't use asynchronous CryptoAPI algorithms Eric Biggers
2025-07-10 6:07 ` Eric Biggers
2025-07-10 6:07 ` [PATCH v2 2/6] fscrypt: Drop FORBID_WEAK_KEYS flag for AES-ECB Eric Biggers
2025-07-10 6:07 ` Eric Biggers
2025-07-10 6:07 ` [PATCH v2 3/6] fscrypt: Switch to sync_skcipher and on-stack requests Eric Biggers
2025-07-10 6:07 ` Eric Biggers
2025-07-10 6:07 ` [PATCH v2 4/6] fscrypt: Remove gfp_t argument from fscrypt_crypt_data_unit() Eric Biggers
2025-07-10 6:07 ` Eric Biggers
2025-07-10 6:07 ` [PATCH v2 5/6] fscrypt: Remove gfp_t argument from fscrypt_encrypt_block_inplace() Eric Biggers
2025-07-10 6:07 ` Eric Biggers
2025-07-10 11:08 ` Alex Markuze
2025-07-10 11:08 ` Alex Markuze
2025-07-10 6:07 ` [PATCH v2 6/6] ceph: Remove gfp_t argument from ceph_fscrypt_encrypt_*() Eric Biggers
2025-07-10 6:07 ` Eric Biggers
2025-07-10 11:07 ` Alex Markuze
2025-07-10 11:07 ` Alex Markuze
2025-07-10 19:32 ` Eric Biggers
2025-07-10 19:32 ` 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=20250710060754.637098-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.