From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrey Albershteyn <aalbersh@kernel.org>
Cc: linux-xfs@vger.kernel.org, fsverity@lists.linux.dev,
linux-fsdevel@vger.kernel.org, ebiggers@kernel.org, hch@lst.de,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v14 14/21] xfs: add flags to xfs_free_eofblocks() to pass down to block processing
Date: Tue, 4 Aug 2026 11:18:48 -0700 [thread overview]
Message-ID: <20260804181848.GM3556460@frogsfrogsfrogs> (raw)
In-Reply-To: <20260803200820.393203-15-aalbersh@kernel.org>
On Mon, Aug 03, 2026 at 10:08:04PM +0200, Andrey Albershteyn wrote:
> Add a flags parameter to xfs_free_eofblocks() to support selective
> extent unmapping. Add two flags for unmapping all extents (unwritten and
> normal) and fsverity leftover extents (only unwritten ones, leaving
> normal in place).
Er, why do we need this? Is this to clear out unwritten merkle tree
blocks after a failed fsverity enrollment or something? The commit
message should say a little bit more about why anyone needs this.
> Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
> ---
> fs/xfs/libxfs/xfs_bmap.c | 56 +++++++++++++++++++++++++++++-----------
> fs/xfs/libxfs/xfs_bmap.h | 6 ++++-
> fs/xfs/xfs_bmap_util.c | 20 ++++++++++----
> fs/xfs/xfs_bmap_util.h | 13 +++++++++-
> fs/xfs/xfs_file.c | 2 +-
> fs/xfs/xfs_icache.c | 2 +-
> fs/xfs/xfs_inode.c | 2 +-
> 7 files changed, 76 insertions(+), 25 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_bmap.c b/fs/xfs/libxfs/xfs_bmap.c
> index cc48f6e20e80..1d8d157a9dfa 100644
> --- a/fs/xfs/libxfs/xfs_bmap.c
> +++ b/fs/xfs/libxfs/xfs_bmap.c
> @@ -6144,15 +6144,12 @@ xfs_bmap_validate_extent(
> XFS_IS_REALTIME_INODE(ip), whichfork, irec);
> }
>
> -/*
> - * Used in xfs_itruncate_extents(). This is the maximum number of extents
> - * freed from a file in a single transaction.
> - */
> -#define XFS_ITRUNC_MAX_EXTENTS 2
> -
> /*
> * Unmap every extent in part of an inode's fork. We don't do any higher level
> * invalidation work at all.
> + *
> + * The XFS_BMAPI_UNWRITTEN could be passed to remove only unwritten extents,
> + * leaving out normal extents in place.
What flags do we support here? ATTRFORK, NODISCARD, and UNWRITTEN? Can
that be documented in the comment or turned into asserts?
> */
> int
> xfs_bunmapi_range(
> @@ -6162,23 +6159,52 @@ xfs_bunmapi_range(
> xfs_fileoff_t startoff,
> xfs_fileoff_t endoff)
> {
> - xfs_filblks_t unmap_len = endoff - startoff + 1;
> int error = 0;
> + int nimaps = 1;
> + int done = 0;
> + struct xfs_bmbt_irec imap;
> + int read_flags =
> + flags & (XFS_BMAPI_ATTRFORK | XFS_BMAPI_ENTIRE);
Why BMAPI_ENTIRE?
> + xfs_exntst_t exntst = XFS_EXT_NORM;
>
> xfs_assert_ilocked(ip, XFS_ILOCK_EXCL);
>
> - while (unmap_len > 0) {
> - ASSERT((*tpp)->t_highest_agno == NULLAGNUMBER);
> - error = __xfs_bunmapi(*tpp, ip, startoff, &unmap_len, flags,
> - XFS_ITRUNC_MAX_EXTENTS);
> + if (flags & XFS_BMAPI_UNWRITTEN)
> + exntst = XFS_EXT_UNWRITTEN;
> +
> + while (startoff < endoff) {
> + nimaps = 1;
> +
> + error = xfs_bmapi_read(ip, startoff, endoff - startoff + 1,
> + &imap, &nimaps, read_flags);
> if (error)
> goto out;
>
> - /* free the just unmapped extents */
> - error = xfs_defer_finish(tpp);
> - if (error)
> + if (nimaps == 0)
> goto out;
> - cond_resched();
> +
> + if ((exntst == XFS_EXT_UNWRITTEN) &&
> + (imap.br_state != exntst)) {
No need for parentheses around these condition checks.
Would it be clearer if this was:
/* caller only wants to unmap unwritten extents */
if ((flags & XFS_BMAPI_UNWRITTEN) &&
imap.br_state != XFS_EXT_UNWRITTEN) {
...
}
> + startoff = imap.br_startoff + imap.br_blockcount;
> + continue;
> + }
> +
> + done = 0;
> + while (!done) {
> + ASSERT((*tpp)->t_highest_agno == NULLAGNUMBER);
> + error = xfs_bunmapi(*tpp, ip, imap.br_startoff,
> + imap.br_blockcount, flags, 0, &done);
> + if (error)
> + goto out;
> +
> + /* free the just unmapped extent */
> + error = xfs_defer_finish(tpp);
> + if (error)
> + goto out;
> + cond_resched();
> + }
> +
> + startoff = imap.br_startoff + imap.br_blockcount;
> }
> out:
> return error;
> diff --git a/fs/xfs/libxfs/xfs_bmap.h b/fs/xfs/libxfs/xfs_bmap.h
> index d5f2729305fa..0f36431d9936 100644
> --- a/fs/xfs/libxfs/xfs_bmap.h
> +++ b/fs/xfs/libxfs/xfs_bmap.h
> @@ -90,6 +90,9 @@ struct xfs_bmalloca {
> /* Try to align allocations to the extent size hint */
> #define XFS_BMAPI_EXTSZALIGN (1u << 11)
>
> +/* Process unwritten extents only. Used for unmapping */
> +#define XFS_BMAPI_UNWRITTEN (1u << 12)
> +
> #define XFS_BMAPI_FLAGS \
> { XFS_BMAPI_ENTIRE, "ENTIRE" }, \
> { XFS_BMAPI_METADATA, "METADATA" }, \
> @@ -102,7 +105,8 @@ struct xfs_bmalloca {
> { XFS_BMAPI_COWFORK, "COWFORK" }, \
> { XFS_BMAPI_NODISCARD, "NODISCARD" }, \
> { XFS_BMAPI_NORMAP, "NORMAP" },\
> - { XFS_BMAPI_EXTSZALIGN, "EXTSZALIGN" }
> + { XFS_BMAPI_EXTSZALIGN, "EXTSZALIGN" }, \
> + { XFS_BMAPI_UNWRITTEN, "UNWRITTEN" }
>
>
> static inline int xfs_bmapi_aflag(int w)
> diff --git a/fs/xfs/xfs_bmap_util.c b/fs/xfs/xfs_bmap_util.c
> index c88b9ade7389..6323eac48fc8 100644
> --- a/fs/xfs/xfs_bmap_util.c
> +++ b/fs/xfs/xfs_bmap_util.c
> @@ -574,11 +574,13 @@ xfs_can_free_eofblocks(
> */
> int
> xfs_free_eofblocks(
> - struct xfs_inode *ip)
> + struct xfs_inode *ip,
> + int flags)
> {
> struct xfs_trans *tp;
> struct xfs_mount *mp = ip->i_mount;
> int error;
> + int bmapi_flags = XFS_BMAPI_NODISCARD;
>
> /* Attach the dquots to the inode up front. */
> error = xfs_qm_dqattach(ip);
> @@ -593,15 +595,20 @@ xfs_free_eofblocks(
> *
> * Note that this means we also leave speculative preallocations in
> * place for preallocated files.
> + *
> + * Clean up delalloc reservations for fsverity too as those won't be
> + * used
> */
> - if (ip->i_diflags & (XFS_DIFLAG_PREALLOC | XFS_DIFLAG_APPEND)) {
> + if (ip->i_diflags & (XFS_DIFLAG_PREALLOC | XFS_DIFLAG_APPEND) ||
> + (flags & XFS_FREE_FSVERITY)) {
Oh, this patch keeps going after adding new flags to xfs_bunmapi.
Uh, this part should be a separate patch then.
> if (ip->i_delayed_blks) {
> xfs_bmap_punch_delalloc_range(ip, XFS_DATA_FORK,
> round_up(XFS_ISIZE(ip), mp->m_sb.sb_blocksize),
> LLONG_MAX, NULL);
> }
> xfs_inode_clear_eofblocks_tag(ip);
> - return 0;
> + if (!(flags & XFS_FREE_FSVERITY))
> + return 0;
> }
>
> error = xfs_trans_alloc(mp, &M_RES(mp)->tr_itruncate, 0, 0, 0, &tp);
> @@ -613,6 +620,9 @@ xfs_free_eofblocks(
> xfs_ilock(ip, XFS_ILOCK_EXCL);
> xfs_trans_ijoin(tp, ip, 0);
>
> + if (flags & XFS_FREE_FSVERITY)
> + bmapi_flags |= XFS_BMAPI_UNWRITTEN;
> +
> /*
> * Do not update the on-disk file size. If we update the on-disk file
> * size and then the system crashes before the contents of the file are
> @@ -620,7 +630,7 @@ xfs_free_eofblocks(
> * bug).
> */
> error = xfs_itruncate_extents_flags(&tp, ip, XFS_DATA_FORK,
> - XFS_ISIZE(ip), XFS_BMAPI_NODISCARD);
> + XFS_ISIZE(ip), bmapi_flags);
> if (error)
> goto err_cancel;
>
> @@ -928,7 +938,7 @@ xfs_prepare_shift(
> * into the accessible region of the file.
> */
> if (xfs_can_free_eofblocks(ip)) {
> - error = xfs_free_eofblocks(ip);
> + error = xfs_free_eofblocks(ip, XFS_FREE_ALL);
> if (error)
> return error;
> }
> diff --git a/fs/xfs/xfs_bmap_util.h b/fs/xfs/xfs_bmap_util.h
> index eaaf094154b9..9ea3000466cc 100644
> --- a/fs/xfs/xfs_bmap_util.h
> +++ b/fs/xfs/xfs_bmap_util.h
> @@ -64,9 +64,20 @@ int xfs_collapse_file_space(struct xfs_inode *, xfs_off_t offset,
> int xfs_insert_file_space(struct xfs_inode *, xfs_off_t offset,
> xfs_off_t len);
>
> +/*
> + * Remove all extents and reservations beyond EOF
> + */
> +#define XFS_FREE_ALL 0
> +
> +/*
> + * Do the normal post EOF cleaning except don't remove normal extents, in other
> + * words, remove unwritten, delayed allocation and cow reservations
IOWs it preserves written blocks storing a merkle tree?
> + */
> +#define XFS_FREE_FSVERITY 1
/me wonders if this should be XFS_FREE_EOF_{ALL,PRESERVE_MERKLE} ?
Also, can we decide this from the XFS_DIFLAG2_VERITY state?
--D
> +
> /* EOF block manipulation functions */
> bool xfs_can_free_eofblocks(struct xfs_inode *ip);
> -int xfs_free_eofblocks(struct xfs_inode *ip);
> +int xfs_free_eofblocks(struct xfs_inode *ip, int flags);
>
> int xfs_swap_extents(struct xfs_inode *ip, struct xfs_inode *tip,
> struct xfs_swapext *sx);
> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> index e9927688086d..43b8fd5a25c5 100644
> --- a/fs/xfs/xfs_file.c
> +++ b/fs/xfs/xfs_file.c
> @@ -1827,7 +1827,7 @@ xfs_file_release(
> xfs_ilock_nowait(ip, XFS_IOLOCK_EXCL)) {
> if (xfs_can_free_eofblocks(ip) &&
> !xfs_iflags_test_and_set(ip, XFS_EOFBLOCKS_RELEASED))
> - xfs_free_eofblocks(ip);
> + xfs_free_eofblocks(ip, XFS_FREE_ALL);
> xfs_iunlock(ip, XFS_IOLOCK_EXCL);
> }
>
> diff --git a/fs/xfs/xfs_icache.c b/fs/xfs/xfs_icache.c
> index 9d8dd30bd927..2b3601bb28c9 100644
> --- a/fs/xfs/xfs_icache.c
> +++ b/fs/xfs/xfs_icache.c
> @@ -1261,7 +1261,7 @@ xfs_inode_free_eofblocks(
> *lockflags |= XFS_IOLOCK_EXCL;
>
> if (xfs_can_free_eofblocks(ip))
> - return xfs_free_eofblocks(ip);
> + return xfs_free_eofblocks(ip, XFS_FREE_ALL);
>
> /* inode could be preallocated */
> trace_xfs_inode_free_eofblocks_invalid(ip);
> diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> index 15279d22a894..63f346e2f1d5 100644
> --- a/fs/xfs/xfs_inode.c
> +++ b/fs/xfs/xfs_inode.c
> @@ -1436,7 +1436,7 @@ xfs_inactive(
> * reference to the inode at this point anyways.
> */
> if (xfs_can_free_eofblocks(ip))
> - error = xfs_free_eofblocks(ip);
> + error = xfs_free_eofblocks(ip, XFS_FREE_ALL);
>
> goto out;
> }
> --
> 2.54.0
>
>
next prev parent reply other threads:[~2026-08-04 18:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 20:07 [PATCH v14 00/21] fs-verity support for XFS with post EOF merkle tree Andrey Albershteyn
2026-08-03 20:07 ` [PATCH v14 01/21] fsverity: report validation errors through fserror to fsnotify Andrey Albershteyn
2026-08-03 20:07 ` [PATCH v14 02/21] fsverity: expose ensure_fsverity_info() Andrey Albershteyn
2026-08-03 20:07 ` [PATCH v14 03/21] fsverity: pass digest size and hash of the all-zeroes block to ->write Andrey Albershteyn
2026-08-03 20:07 ` [PATCH v14 04/21] fsverity: hoist pagecache_read from f2fs/ext4 to fsverity Andrey Albershteyn
2026-08-03 20:07 ` [PATCH v14 05/21] fsverity: improve flushing performance of fsverity_fill_zerohash Andrey Albershteyn
2026-08-04 17:42 ` Christoph Hellwig
2026-08-04 18:37 ` Eric Biggers
2026-08-04 18:57 ` Eric Biggers
2026-08-04 19:00 ` Darrick J. Wong
2026-08-04 18:01 ` Darrick J. Wong
2026-08-04 18:46 ` Matthew Wilcox
2026-08-04 18:56 ` Darrick J. Wong
2026-08-04 19:28 ` Matthew Wilcox
2026-08-03 20:07 ` [PATCH v14 06/21] fsverity: don't allow setting DAX file attribute on fsverity files Andrey Albershteyn
2026-08-04 18:02 ` Darrick J. Wong
2026-08-03 20:07 ` [PATCH v14 07/21] fsverity: hoist statx reporting of fs-verity flag Andrey Albershteyn
2026-08-04 17:39 ` Christoph Hellwig
2026-08-04 18:02 ` Darrick J. Wong
2026-08-03 20:07 ` [PATCH v14 08/21] xfs: introduce fsverity on-disk changes Andrey Albershteyn
2026-08-03 20:07 ` [PATCH v14 09/21] xfs: don't allow to enable DAX on fs-verity sealed inode Andrey Albershteyn
2026-08-03 20:08 ` [PATCH v14 10/21] xfs: disable direct read path for fs-verity files Andrey Albershteyn
2026-08-03 20:08 ` [PATCH v14 11/21] xfs: don't report dio_mem_align and dio_offset_align for fsverity files Andrey Albershteyn
2026-08-04 17:43 ` Christoph Hellwig
2026-08-04 17:50 ` Darrick J. Wong
2026-08-04 18:29 ` Eric Biggers
2026-08-04 18:24 ` Eric Biggers
2026-08-03 20:08 ` [PATCH v14 12/21] xfs: handle fsverity I/O in write/read path Andrey Albershteyn
2026-08-04 18:27 ` Darrick J. Wong
2026-08-03 20:08 ` [PATCH v14 13/21] xfs: use read ioend for fsverity data verification Andrey Albershteyn
2026-08-04 18:36 ` Darrick J. Wong
2026-08-03 20:08 ` [PATCH v14 14/21] xfs: add flags to xfs_free_eofblocks() to pass down to block processing Andrey Albershteyn
2026-08-04 18:18 ` Darrick J. Wong [this message]
2026-08-03 20:08 ` [PATCH v14 15/21] xfs: add fs-verity support Andrey Albershteyn
2026-08-03 20:08 ` [PATCH v14 16/21] xfs: initialize fs-verity on file open Andrey Albershteyn
2026-08-03 20:08 ` [PATCH v14 17/21] xfs: add fs-verity ioctls Andrey Albershteyn
2026-08-03 20:08 ` [PATCH v14 18/21] xfs: advertise fs-verity being available on filesystem Andrey Albershteyn
2026-08-03 20:08 ` [PATCH v14 19/21] xfs: check and repair the verity inode flag state Andrey Albershteyn
2026-08-03 20:08 ` [PATCH v14 20/21] xfs: introduce health state for corrupted fsverity metadata Andrey Albershteyn
2026-08-03 20:08 ` [PATCH v14 21/21] xfs: enable ro-compat fs-verity flag Andrey Albershteyn
2026-08-04 17:35 ` [PATCH v14 00/21] fs-verity support for XFS with post EOF merkle tree Christoph Hellwig
2026-08-04 17:52 ` Darrick J. Wong
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=20260804181848.GM3556460@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@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