From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: fsverity@lists.linux.dev, 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>,
Andrey Albershteyn <aalbersh@redhat.com>,
Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <djwong@kernel.org>,
David Sterba <dsterba@suse.com>, Jan Kara <jack@suse.cz>
Subject: [GIT PULL] fsverity updates for 7.0
Date: Wed, 11 Feb 2026 17:26:52 -0800 [thread overview]
Message-ID: <20260212012652.GA8885@sol> (raw)
The following changes since commit 63804fed149a6750ffd28610c5c1c98cce6bd377:
Linux 6.19-rc7 (2026-01-25 14:11:24 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/fsverity/linux.git tags/fsverity-for-linus
for you to fetch changes up to 433fbcac9ebe491b518b21c7305fba9a748c7d2c:
fsverity: remove inode from fsverity_verification_ctx (2026-02-04 11:31:54 -0800)
----------------------------------------------------------------
fsverity cleanups, speedup, and memory usage optimization from
Christoph Hellwig:
- Move some logic into common code
- Fix btrfs to reject truncates of fsverity files
- Improve the Merkle tree readahead implementation
- Store each inode's fsverity_info in a hash table instead of using a
pointer in the filesystem-specific part of the inode.
This optimizes for memory usage in the usual case where most files
don't have fsverity enabled.
- Look up the fsverity_info fewer times during verification, to
amortize the hash table overhead
----------------------------------------------------------------
Christoph Hellwig (17):
fs,fsverity: reject size changes on fsverity files in setattr_prepare
fs,fsverity: clear out fsverity_info from common code
ext4: don't build the fsverity work handler for !CONFIG_FS_VERITY
f2fs: don't build the fsverity work handler for !CONFIG_FS_VERITY
fsverity: pass struct file to ->write_merkle_tree_block
fsverity: start consolidating pagecache code
fsverity: don't issue readahead for non-ENOENT errors from __filemap_get_folio
readahead: push invalidate_lock out of page_cache_ra_unbounded
ext4: move ->read_folio and ->readahead to readpage.c
fsverity: kick off hash readahead at data I/O submission time
fsverity: deconstify the inode pointer in struct fsverity_info
fsverity: push out fsverity_info lookup
fs: consolidate fsverity_info lookup in buffer.c
ext4: consolidate fsverity_info lookup
f2fs: consolidate fsverity_info lookup
btrfs: consolidate fsverity_info lookup
fsverity: use a hashtable to find the fsverity_info
Eric Biggers (1):
fsverity: remove inode from fsverity_verification_ctx
fs/attr.c | 12 ++-
fs/btrfs/btrfs_inode.h | 4 -
fs/btrfs/extent_io.c | 53 +++++++-----
fs/btrfs/inode.c | 13 +--
fs/btrfs/verity.c | 11 +--
fs/buffer.c | 25 +++---
fs/ext4/ext4.h | 8 +-
fs/ext4/inode.c | 31 -------
fs/ext4/readpage.c | 64 +++++++++++----
fs/ext4/super.c | 4 -
fs/ext4/verity.c | 34 +++-----
fs/f2fs/compress.c | 7 +-
fs/f2fs/data.c | 100 ++++++++++++++---------
fs/f2fs/f2fs.h | 12 +--
fs/f2fs/file.c | 6 +-
fs/f2fs/inode.c | 1 -
fs/f2fs/super.c | 3 -
fs/f2fs/verity.c | 34 +++-----
fs/inode.c | 9 ++
fs/verity/Makefile | 1 +
fs/verity/enable.c | 41 ++++++----
fs/verity/fsverity_private.h | 20 +++--
fs/verity/open.c | 84 +++++++++++--------
fs/verity/pagecache.c | 58 +++++++++++++
fs/verity/read_metadata.c | 19 +++--
fs/verity/verify.c | 91 +++++++++++++--------
include/linux/fsverity.h | 190 +++++++++++++++++--------------------------
mm/readahead.c | 15 ++--
28 files changed, 516 insertions(+), 434 deletions(-)
create mode 100644 fs/verity/pagecache.c
next reply other threads:[~2026-02-12 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 1:26 Eric Biggers [this message]
2026-02-12 10:11 ` [GIT PULL] fsverity updates for 7.0 Christoph Hellwig
2026-02-12 17:38 ` Eric Biggers
2026-02-12 19:13 ` [f2fs-dev] " 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=20260212012652.GA8885@sol \
--to=ebiggers@kernel.org \
--cc=aalbersh@redhat.com \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=fsverity@lists.linux.dev \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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