From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
Yuwen Chen <ywen.chen@foxmail.com>
Subject: [GIT PULL] fscrypt updates for 6.17
Date: Sun, 27 Jul 2025 16:49:36 -0700 [thread overview]
Message-ID: <20250727234936.GE1261@sol> (raw)
The following changes since commit e04c78d86a9699d136910cfc0bdcf01087e3267e:
Linux 6.16-rc2 (2025-06-15 13:49:41 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/fscrypt/linux.git tags/fscrypt-for-linus
for you to fetch changes up to fa65058063cbaba6e519b5291a7e2e9e0fa24ae3:
ceph: Remove gfp_t argument from ceph_fscrypt_encrypt_*() (2025-07-10 12:33:17 -0700)
----------------------------------------------------------------
Simplify how fscrypt uses the crypto API, resulting in some
significant performance improvements:
- Drop the incomplete and problematic support for asynchronous
algorithms. These drivers are bug-prone, and it turns out they are
actually much slower than the CPU-based code as well.
- Allocate crypto requests on the stack instead of the heap. This
improves encryption and decryption performance, especially for
filenames. It also eliminates a point of failure during I/O.
----------------------------------------------------------------
Eric Biggers (9):
fscrypt: Explicitly include <linux/export.h>
fscrypt: Drop obsolete recommendation to enable optimized SHA-512
fscrypt: Don't use problematic non-inline crypto engines
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_*()
Documentation/filesystems/fscrypt.rst | 45 ++++++++---------------
fs/ceph/crypto.c | 13 +++----
fs/ceph/crypto.h | 10 ++---
fs/ceph/file.c | 3 +-
fs/ceph/inode.c | 3 +-
fs/crypto/bio.c | 9 +++--
fs/crypto/crypto.c | 52 ++++++++++----------------
fs/crypto/fname.c | 69 +++++++++++++----------------------
fs/crypto/fscrypt_private.h | 23 ++++++++++--
fs/crypto/hkdf.c | 4 +-
fs/crypto/hooks.c | 2 +
fs/crypto/inline_crypt.c | 1 +
fs/crypto/keyring.c | 5 ++-
fs/crypto/keysetup.c | 23 +++++++-----
fs/crypto/keysetup_v1.c | 55 ++++++++++++----------------
fs/crypto/policy.c | 4 +-
fs/ubifs/crypto.c | 2 +-
include/linux/fscrypt.h | 5 +--
18 files changed, 146 insertions(+), 182 deletions(-)
next reply other threads:[~2025-07-27 23:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 23:49 Eric Biggers [this message]
2025-07-29 1:12 ` [GIT PULL] fscrypt updates for 6.17 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=20250727234936.GE1261@sol \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--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;
as well as URLs for NNTP newsgroup(s).