Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Andrey Albershteyn <aalbersh@kernel.org>
To: linux-xfs@vger.kernel.org, fsverity@lists.linux.dev,
	linux-fsdevel@vger.kernel.org, ebiggers@kernel.org
Cc: Andrey Albershteyn <aalbersh@kernel.org>,
	hch@lst.de, linux-ext4@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-btrfs@vger.kernel.org, linux-unionfs@vger.kernel.org,
	djwong@kernel.org
Subject: [PATCH v10 17/22] xfs: remove unwritten extents after preallocations in fsverity metadata
Date: Wed, 20 May 2026 14:37:15 +0200	[thread overview]
Message-ID: <20260520123722.405752-18-aalbersh@kernel.org> (raw)
In-Reply-To: <20260520123722.405752-1-aalbersh@kernel.org>

XFS preallocates spaces during writes. In normal I/O this space, if
unused, is removed by truncate. For files with fsverity XFS does not use
truncate as fsverity metadata is stored past EOF.

After we're done with writing fsverity metadata iterate over extents in
that region and remove any unwritten ones. These would be left overs in
the holes in the merkle tree and past fsverity descriptor.

Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
---
 fs/xfs/xfs_fsverity.c | 69 +++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 69 insertions(+)

diff --git a/fs/xfs/xfs_fsverity.c b/fs/xfs/xfs_fsverity.c
index a06885291412..298d712b5ba2 100644
--- a/fs/xfs/xfs_fsverity.c
+++ b/fs/xfs/xfs_fsverity.c
@@ -21,6 +21,8 @@
 #include "xfs_iomap.h"
 #include "xfs_error.h"
 #include "xfs_health.h"
+#include "xfs_bmap.h"
+#include "xfs_bmap_util.h"
 #include <linux/fsverity.h>
 #include <linux/iomap.h>
 #include <linux/pagemap.h>
@@ -171,6 +173,65 @@ xfs_fsverity_delete_metadata(
 	return error;
 }
 
+static int
+xfs_fsverity_cancel_unwritten(
+	struct xfs_inode	*ip,
+	loff_t			start,
+	loff_t			end)
+{
+	struct xfs_mount	*mp = ip->i_mount;
+	struct xfs_trans	*tp;
+	xfs_fileoff_t		offset_fsb = XFS_B_TO_FSB(mp, start);
+	xfs_fileoff_t		end_fsb = XFS_B_TO_FSB(mp, end);
+	struct xfs_bmbt_irec	imap;
+	int			nimaps;
+	int			error = 0;
+	int			done;
+
+
+	while (offset_fsb < end_fsb) {
+		nimaps = 1;
+
+		error = xfs_trans_alloc(mp, &M_RES(mp)->tr_write, 0, 0,
+				0, &tp);
+		if (error)
+			return error;
+
+		xfs_ilock(ip, XFS_ILOCK_EXCL);
+		error = xfs_bmapi_read(ip, offset_fsb, end_fsb - offset_fsb,
+				&imap, &nimaps, 0);
+		if (error)
+			goto out_cancel;
+
+		if (nimaps == 0)
+			goto out_cancel;
+
+		if (imap.br_state == XFS_EXT_UNWRITTEN) {
+			xfs_trans_ijoin(tp, ip, 0);
+
+			error = xfs_bunmapi(tp, ip, imap.br_startoff,
+					imap.br_blockcount, 0, 1, &done);
+			if (error)
+				goto out_cancel;
+
+			error = xfs_trans_commit(tp);
+			if (error)
+				return error;
+		} else {
+			xfs_trans_cancel(tp);
+		}
+		xfs_iunlock(ip, XFS_ILOCK_EXCL);
+
+		offset_fsb = imap.br_startoff + imap.br_blockcount;
+	}
+
+	return error;
+out_cancel:
+	xfs_trans_cancel(tp);
+	xfs_iunlock(ip, XFS_ILOCK_EXCL);
+	return error;
+}
+
 
 /*
  * Prepare to enable fsverity by clearing old metadata.
@@ -248,6 +309,14 @@ xfs_fsverity_end_enable(
 	if (error)
 		goto out;
 
+	/*
+	 * Remove unwritten extents left by COW preallocations and write
+	 * preallocation in the merkle tree holes and past descriptor
+	 */
+	error = xfs_fsverity_cancel_unwritten(ip, range_start, LLONG_MAX);
+	if (error)
+		goto out;
+
 	/*
 	 * Proactively drop any delayed allocations in COW fork, the fsverity
 	 * files are read-only
-- 
2.51.2


  parent reply	other threads:[~2026-05-20 12:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20 12:36 [PATCH v10 00/22] fs-verity support for XFS with post EOF merkle tree Andrey Albershteyn
2026-05-20 12:36 ` [PATCH v10 01/22] fsverity: report validation errors through fserror to fsnotify Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 02/22] fsverity: expose ensure_fsverity_info() Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 03/22] ovl: use core fsverity ensure info interface Andrey Albershteyn
2026-05-20 12:54   ` Andrey Albershteyn
2026-05-20 13:00     ` Andrey Albershteyn
2026-05-20 13:24     ` Amir Goldstein
2026-05-20 19:07   ` Eric Biggers
2026-05-20 12:37 ` [PATCH v10 04/22] fsverity: generate and store zero-block hash Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 05/22] fsverity: pass digest size and hash of the all-zeroes block to ->write Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 06/22] fsverity: hoist pagecache_read from f2fs/ext4 to fsverity Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 07/22] iomap: introduce IOMAP_F_FSVERITY and teach writeback to handle fsverity Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 08/22] iomap: teach iomap to read files with fsverity Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 09/22] iomap: introduce iomap_fsverity_write() for writing fsverity metadata Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 10/22] xfs: introduce fsverity on-disk changes Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 11/22] xfs: initialize fs-verity on file open Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 12/22] xfs: don't allow to enable DAX on fs-verity sealed inode Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 13/22] xfs: disable direct read path for fs-verity files Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 14/22] xfs: handle fsverity I/O in write/read path Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 15/22] xfs: use read ioend for fsverity data verification Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 16/22] xfs: add fs-verity support Andrey Albershteyn
2026-05-20 12:37 ` Andrey Albershteyn [this message]
2026-05-20 12:37 ` [PATCH v10 18/22] xfs: add fs-verity ioctls Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 19/22] xfs: advertise fs-verity being available on filesystem Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 20/22] xfs: check and repair the verity inode flag state Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 21/22] xfs: introduce health state for corrupted fsverity metadata Andrey Albershteyn
2026-05-20 12:37 ` [PATCH v10 22/22] xfs: enable ro-compat fs-verity flag Andrey Albershteyn
2026-05-21  9:07 ` [PATCH v10 00/22] fs-verity support for XFS with post EOF merkle tree Christoph Hellwig
2026-05-21  9:42   ` Andrey Albershteyn
2026-05-21 11:38     ` Carlos Maiolino
2026-05-21 11:42       ` Carlos Maiolino
2026-05-22  2:06         ` Eric Biggers
2026-05-22 10:03       ` Christian Brauner
2026-05-22 12:07         ` Christoph Hellwig
2026-05-26 10:19           ` Carlos Maiolino

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=20260520123722.405752-18-aalbersh@kernel.org \
    --to=aalbersh@kernel.org \
    --cc=djwong@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=fsverity@lists.linux.dev \
    --cc=hch@lst.de \
    --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-unionfs@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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