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, djwong@kernel.org
Subject: [PATCH v12 15/21] xfs: remove unwritten extents after preallocations in fsverity metadata
Date: Mon, 20 Jul 2026 11:03:43 +0200 [thread overview]
Message-ID: <20260720090410.3487990-16-aalbersh@kernel.org> (raw)
In-Reply-To: <20260720090410.3487990-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.
Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
---
fs/xfs/xfs_fsverity.c | 79 +++++++++++++++++++++++++++++++++++++++++++
1 file changed, 79 insertions(+)
diff --git a/fs/xfs/xfs_fsverity.c b/fs/xfs/xfs_fsverity.c
index 4606354894e1..7dd7aec646cf 100644
--- a/fs/xfs/xfs_fsverity.c
+++ b/fs/xfs/xfs_fsverity.c
@@ -12,12 +12,15 @@
#include "xfs_inode.h"
#include "xfs_log_format.h"
#include "xfs_trans.h"
+#include "xfs_defer.h"
#include "xfs_trace.h"
#include "xfs_quota.h"
#include "xfs_fsverity.h"
#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>
@@ -179,6 +182,74 @@ 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_FSBT(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) {
+ done = 0;
+
+ xfs_trans_ijoin(tp, ip, 0);
+
+ while (!done) {
+ error = xfs_bunmapi(tp, ip, imap.br_startoff,
+ imap.br_blockcount, 0, 1,
+ &done);
+ if (error)
+ goto out_cancel;
+
+ error = xfs_defer_finish(&tp);
+ if (error)
+ goto out_cancel;
+ }
+
+ error = xfs_trans_commit(tp);
+ if (error)
+ goto out_unlock;
+ } 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);
+out_unlock:
+ xfs_iunlock(ip, XFS_ILOCK_EXCL);
+ return error;
+}
+
/*
* Prepare to enable fsverity by clearing old metadata.
@@ -262,6 +333,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.54.0
next prev parent reply other threads:[~2026-07-20 9:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 9:03 [PATCH v12 00/21] fs-verity support for XFS with post EOF merkle tree Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 01/21] fsverity: report validation errors through fserror to fsnotify Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 02/21] fsverity: expose ensure_fsverity_info() Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 03/21] fsverity: pass digest size and hash of the all-zeroes block to ->write Andrey Albershteyn
2026-07-21 2:58 ` David Sterba
2026-07-20 9:03 ` [PATCH v12 04/21] fsverity: hoist pagecache_read from f2fs/ext4 to fsverity Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 05/21] fsverity: improve flushing performance of fsverity_fill_zerohash Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 06/21] fsverity: don't allow setting DAX file attribute on fsverity files Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 07/21] fs,fsverity: remove check for fsverity being enabled in setattr_prepare() Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 08/21] xfs: introduce fsverity on-disk changes Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 09/21] xfs: don't allow to enable DAX on fs-verity sealed inode Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 10/21] xfs: disable direct read path for fs-verity files Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 11/21] xfs: don't report dio_mem_align and dio_offset_align for fsverity files Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 12/21] xfs: handle fsverity I/O in write/read path Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 13/21] xfs: use read ioend for fsverity data verification Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 14/21] xfs: add fs-verity support Andrey Albershteyn
2026-07-20 9:03 ` Andrey Albershteyn [this message]
2026-07-20 9:03 ` [PATCH v12 16/21] xfs: initialize fs-verity on file open Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 17/21] xfs: add fs-verity ioctls Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 18/21] xfs: advertise fs-verity being available on filesystem Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 19/21] xfs: check and repair the verity inode flag state Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 20/21] xfs: introduce health state for corrupted fsverity metadata Andrey Albershteyn
2026-07-20 9:03 ` [PATCH v12 21/21] xfs: enable ro-compat fs-verity flag Andrey Albershteyn
2026-07-21 8:46 ` [PATCH v12 00/21] fs-verity support for XFS with post EOF merkle tree Andrey Albershteyn
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=20260720090410.3487990-16-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-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