[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250810075706.172910-1-ebiggers@kernel.org>
Date: Sun, 10 Aug 2025 00:56:53 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: linux-fscrypt@...r.kernel.org,
fsverity@...ts.linux.dev
Cc: linux-fsdevel@...r.kernel.org,
linux-ext4@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net,
linux-mtd@...ts.infradead.org,
linux-btrfs@...r.kernel.org,
ceph-devel@...r.kernel.org,
Christian Brauner <brauner@...nel.org>,
Eric Biggers <ebiggers@...nel.org>
Subject: [PATCH v5 00/13] Move fscrypt and fsverity info out of struct inode
This is a cleaned-up implementation of moving the i_crypt_info and
i_verity_info pointers out of 'struct inode' and into the fs-specific
part of the inode, as proposed previously by Christian at
https://lore.kernel.org/r/20250723-work-inode-fscrypt-v4-0-c8e11488a0e6@kernel.org/
The high-level concept is still the same: fs/crypto/ and fs/verity/
locate the pointer by adding an offset to the address of struct inode.
The offset is retrieved from fscrypt_operations or fsverity_operations.
I've cleaned up a lot of the details, including:
- Grouped changes into patches differently
- Rewrote commit messages and comments to be clearer
- Adjusted code formatting to be consistent with existing code
- Removed unneeded #ifdefs
- Improved choice and location of VFS_WARN_ON_ONCE() statements
- Added missing kerneldoc for ubifs_inode::i_crypt_info
- Moved field initialization to init_once functions when they exist
- Improved ceph offset calculation and removed unneeded static_asserts
- fsverity_get_info() now checks IS_VERITY() instead of v_ops
- fscrypt_put_encryption_info() no longer checks IS_ENCRYPTED(), since I
no longer think it's actually correct there.
- verity_data_blocks() now keeps doing a raw dereference
- Dropped fscrypt_set_inode_info()
- Renamed some functions
- Do offset calculation using int, so we don't rely on unsigned overflow
- And more.
For v4 and earlier, see
https://lore.kernel.org/r/20250723-work-inode-fscrypt-v4-0-c8e11488a0e6@kernel.org/
I'd like to take this series through the fscrypt tree for 6.18.
(fsverity normally has a separate tree, but by choosing just one tree
for this, we'll avoid conflicts in some places.)
Eric Biggers (13):
fscrypt: replace raw loads of info pointer with helper function
fscrypt: add support for info in fs-specific part of inode
ext4: move crypt info pointer to fs-specific part of inode
f2fs: move crypt info pointer to fs-specific part of inode
ubifs: move crypt info pointer to fs-specific part of inode
ceph: move crypt info pointer to fs-specific part of inode
fs: remove inode::i_crypt_info
fsverity: add support for info in fs-specific part of inode
ext4: move verity info pointer to fs-specific part of inode
f2fs: move verity info pointer to fs-specific part of inode
btrfs: move verity info pointer to fs-specific part of inode
fs: remove inode::i_verity_info
fsverity: check IS_VERITY() in fsverity_cleanup_inode()
fs/btrfs/btrfs_inode.h | 5 ++++
fs/btrfs/inode.c | 3 ++
fs/btrfs/verity.c | 2 ++
fs/ceph/crypto.c | 2 ++
fs/ceph/inode.c | 1 +
fs/ceph/super.h | 1 +
fs/crypto/bio.c | 2 +-
fs/crypto/crypto.c | 14 +++++----
fs/crypto/fname.c | 11 +++----
fs/crypto/fscrypt_private.h | 4 +--
fs/crypto/hooks.c | 2 +-
fs/crypto/inline_crypt.c | 12 ++++----
fs/crypto/keysetup.c | 43 ++++++++++++++++-----------
fs/crypto/policy.c | 7 +++--
fs/ext4/crypto.c | 2 ++
fs/ext4/ext4.h | 8 +++++
fs/ext4/super.c | 6 ++++
fs/ext4/verity.c | 2 ++
fs/f2fs/f2fs.h | 6 ++++
fs/f2fs/super.c | 10 ++++++-
fs/f2fs/verity.c | 2 ++
fs/ubifs/crypto.c | 2 ++
fs/ubifs/ubifs.h | 4 +++
fs/verity/enable.c | 6 ++--
fs/verity/fsverity_private.h | 9 +++---
fs/verity/open.c | 23 ++++++++-------
fs/verity/verify.c | 2 +-
include/linux/fs.h | 10 -------
include/linux/fscrypt.h | 40 +++++++++++++++++++++++--
include/linux/fsverity.h | 57 +++++++++++++++++++++++++++++-------
30 files changed, 215 insertions(+), 83 deletions(-)
base-commit: 561c80369df0733ba0574882a1635287b20f9de2
--
2.50.1
Powered by blists - more mailing lists