mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: fsverity@lists.linux.dev, linux-xfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Theodore Ts'o <tytso@mit.edu>,
	Andrey Albershteyn <aalbersh@kernel.org>
Subject: [GIT PULL] fsverity updates for 7.4
Date: Sun, 18 Oct 2026 19:37:29 -0700	[thread overview]
Message-ID: <20261019023729.GC3270@sol> (raw)

The following changes since commit fd73f4a6659897191fa0d40695fe370925dd3780:

  Linux 7.3-rc3 (2026-09-13 14:38:02 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/fs/fsverity/linux.git tags/fsverity-for-linus

for you to fetch changes up to f9e450420da2624c93ce9585deebfabb87932774:

  fsverity: hoist statx reporting of fs-verity flag (2026-10-04 19:47:47 +0200)

----------------------------------------------------------------

Patches from Andrey Albershteyn to prepare for XFS fsverity support:

- Report verification errors through fserror, instead of only through
  an unstructured log message and generic I/O error return

- Move the reporting of STATX_ATTR_VERITY into the VFS, so that each
  fsverity-capable filesystem doesn't need to do it. This also fixes a
  bug where btrfs didn't return STATX_ATTR_VERITY in attributes_mask

- Make the VFS prevent enabling DAX on fsverity files, so that it will
  be handled in a single place for ext4 and XFS

- Move ext4 and f2fs's code to read verity metadata from the pagecache
  into shared code, so that XFS will be able to use it too

- Export fsverity_ensure_verity_info() for XFS scrub to use

- Pass all-zeroes hash to ->write_merkle_tree_block() so that XFS will
  be able to implement an optimization for sparse files

----------------------------------------------------------------
Andrey Albershteyn (6):
      fsverity: report validation errors through fserror to fsnotify
      fsverity: expose ensure_fsverity_info()
      fsverity: pass digest size and hash of the all-zeroes block to ->write
      fsverity: hoist pagecache_read from f2fs/ext4 to fsverity
      fsverity: don't allow setting DAX file attribute on fsverity files
      fsverity: hoist statx reporting of fs-verity flag

Eric Biggers (1):
      MAINTAINERS: List the fsverity branches

 MAINTAINERS              |  3 ++-
 fs/btrfs/inode.c         |  3 ---
 fs/btrfs/verity.c        |  6 +++++-
 fs/ext4/inode.c          |  5 +----
 fs/ext4/verity.c         | 36 ++++++------------------------------
 fs/f2fs/file.c           |  5 +----
 fs/f2fs/verity.c         | 34 ++++------------------------------
 fs/file_attr.c           | 11 ++++++++---
 fs/stat.c                |  6 +++++-
 fs/verity/enable.c       |  4 +++-
 fs/verity/open.c         | 26 ++++++++++++++++++++++++--
 fs/verity/pagecache.c    | 33 +++++++++++++++++++++++++++++++++
 fs/verity/verify.c       |  4 ++++
 include/linux/fsverity.h | 10 +++++++++-
 14 files changed, 105 insertions(+), 81 deletions(-)

                 reply	other threads:[~2026-10-19  2:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261019023729.GC3270@sol \
    --to=ebiggers@kernel.org \
    --cc=aalbersh@kernel.org \
    --cc=fsverity@lists.linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@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

all inboxes | Powered by JetHome®