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>, Christoph Hellwig <hch@lst.de>
Subject: [GIT PULL] fscrypt updates for 7.1
Date: Sat, 11 Apr 2026 17:18:20 -0700 [thread overview]
Message-ID: <20260412001820.GA6632@sol> (raw)
The following changes since commit 1f318b96cc84d7c2ab792fcc0bfd42a7ca890681:
Linux 7.0-rc3 (2026-03-08 16:56:54 -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 1546d3feb5e533fbee6710bd51b2847b2ec23623:
fscrypt: use AES library for v1 key derivation (2026-03-25 12:06:33 -0700)
----------------------------------------------------------------
- Various cleanups for the interface between fs/crypto/ and
filesystems, from Christoph Hellwig
- Simplify and optimize the implementation of v1 key derivation by
using the AES library instead of the crypto_skcipher API
----------------------------------------------------------------
Christoph Hellwig (14):
ext4: initialize the write hint in io_submit_init_bio
ext4: open code fscrypt_set_bio_crypt_ctx_bh
ext4: factor out a io_submit_need_new_bio helper
ext4, fscrypt: merge fscrypt_mergeable_bio_bh into io_submit_need_new_bio
fscrypt: move fscrypt_set_bio_crypt_ctx_bh to buffer.c
fscrypt: pass a byte offset to fscrypt_generate_dun
fscrypt: pass a byte offset to fscrypt_mergeable_bio
fscrypt: pass a byte offset to fscrypt_set_bio_crypt_ctx
fscrypt: pass a byte offset to fscrypt_zeroout_range_inline_crypt
fscrypt: pass a byte length to fscrypt_zeroout_range_inline_crypt
fscrypt: pass a byte offset to fscrypt_zeroout_range
fscrypt: pass a byte length to fscrypt_zeroout_range
fscrypt: pass a real sector_t to fscrypt_zeroout_range
ext4: use a byte granularity cursor in ext4_mpage_readpages
Eric Biggers (1):
fscrypt: use AES library for v1 key derivation
fs/buffer.c | 18 +++++++++-
fs/crypto/Kconfig | 2 +-
fs/crypto/bio.c | 38 +++++++++-----------
fs/crypto/fscrypt_private.h | 3 --
fs/crypto/inline_crypt.c | 86 +++++---------------------------------------
fs/crypto/keysetup.c | 2 --
fs/crypto/keysetup_v1.c | 87 +++++++++++++++------------------------------
fs/ext4/inode.c | 5 ++-
fs/ext4/page-io.c | 28 +++++++++++----
fs/ext4/readpage.c | 10 +++---
fs/f2fs/data.c | 7 ++--
fs/f2fs/file.c | 4 ++-
fs/iomap/direct-io.c | 6 ++--
include/linux/fscrypt.h | 37 +++++--------------
14 files changed, 120 insertions(+), 213 deletions(-)
next reply other threads:[~2026-04-12 0:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 0:18 Eric Biggers [this message]
2026-04-14 0:37 ` [GIT PULL] fscrypt updates for 7.1 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=20260412001820.GA6632@sol \
--to=ebiggers@kernel.org \
--cc=hch@lst.de \
--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 \
/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.