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-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Theodore Ts'o <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [GIT PULL] fscrypt updates for 6.7
Date: Sun, 29 Oct 2023 21:04:19 -0700 [thread overview]
Message-ID: <20231030040419.GA43439@sol.localdomain> (raw)
The following changes since commit 6465e260f48790807eef06b583b38ca9789b6072:
Linux 6.6-rc3 (2023-09-24 14:31:13 -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 15baf55481de700f8c4494cddb80ec4f4575548b:
fscrypt: track master key presence separately from secret (2023-10-16 21:23:45 -0700)
----------------------------------------------------------------
This update adds support for configuring the crypto data unit size (i.e.
the granularity of file contents encryption) to be less than the
filesystem block size. This can allow users to use inline encryption
hardware in some cases when it wouldn't otherwise be possible.
In addition, there are two commits that are prerequisites for the
extent-based encryption support that the btrfs folks are working on.
----------------------------------------------------------------
Eric Biggers (6):
fscrypt: make it clearer that key_prefix is deprecated
fscrypt: make the bounce page pool opt-in instead of opt-out
fscrypt: compute max_lblk_bits from s_maxbytes and block size
fscrypt: replace get_ino_and_lblk_bits with just has_32bit_inodes
fscrypt: support crypto data unit size less than filesystem block size
fscrypt: track master key presence separately from secret
Josef Bacik (1):
fscrypt: rename fscrypt_info => fscrypt_inode_info
Documentation/filesystems/fscrypt.rst | 121 ++++++++++++++++++-------
fs/ceph/crypto.c | 1 +
fs/crypto/bio.c | 39 ++++----
fs/crypto/crypto.c | 163 ++++++++++++++++++---------------
fs/crypto/fname.c | 6 +-
fs/crypto/fscrypt_private.h | 164 ++++++++++++++++++++++------------
fs/crypto/hooks.c | 4 +-
fs/crypto/inline_crypt.c | 32 +++----
fs/crypto/keyring.c | 82 ++++++++++-------
fs/crypto/keysetup.c | 62 +++++++------
fs/crypto/keysetup_v1.c | 20 +++--
fs/crypto/policy.c | 83 +++++++++++------
fs/ext4/crypto.c | 13 +--
fs/f2fs/super.c | 13 +--
fs/ubifs/crypto.c | 3 +-
include/linux/fs.h | 4 +-
include/linux/fscrypt.h | 82 ++++++++++-------
include/uapi/linux/fscrypt.h | 3 +-
18 files changed, 546 insertions(+), 349 deletions(-)
next reply other threads:[~2023-10-30 4:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 4:04 Eric Biggers [this message]
2023-10-30 23:50 ` [GIT PULL] fscrypt updates for 6.7 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=20231030040419.GA43439@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 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).