linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>,
	Hans Holmberg <hans.holmberg@wdc.com>,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/7] xfs: don't allocate the xfs_extent_busy structure for zoned RTGs
Date: Wed, 16 Jul 2025 08:50:49 -0700	[thread overview]
Message-ID: <20250716155049.GH2672049@frogsfrogsfrogs> (raw)
In-Reply-To: <20250716125413.2148420-2-hch@lst.de>

On Wed, Jul 16, 2025 at 02:54:01PM +0200, Christoph Hellwig wrote:
> Busy extent tracking is primarily used to ensure that freed blocks are
> not reused for data allocations before the transaction that deleted them
> has been committed to stable storage, and secondarily to drive online
> discard.  None of the use cases applies to zoned RTGs, as the zoned
> allocator can't overwrite blocks before resetting the zone, which already
> flushes out all transactions touching the RTGs.
> 
> So the busy extent tracking is not needed for zoned RTGs, and also not
> called for zoned RTGs.  But somehow the code to skip allocating and
> freeing the structure got lost during the zoned XFS upstreaming process.
> This not only causes these structures to unessecarily allocated, but can

nit: unnecessarily

> also lead to memory leaks as the xg_busy_extents pointer in the
> xfs_group structure is overlayed with the pointer for the linked list
> of to be reset zones.
> 
> Stop allocating and freeing the structure to not pointlessly allocate
> memory which is then leaked when the zone is reset.

Yikes!

Cc: <stable@vger.kernel.org> # v6.15

> Fixes: 080d01c41d44 ("xfs: implement zoned garbage collection")
> Signed-off-by: Christoph Hellwig <hch@lst.de>

With those added,
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D

> ---
>  fs/xfs/libxfs/xfs_group.c | 14 +++++++++-----
>  fs/xfs/xfs_extent_busy.h  |  8 ++++++++
>  2 files changed, 17 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_group.c b/fs/xfs/libxfs/xfs_group.c
> index e9d76bcdc820..20ad7c309489 100644
> --- a/fs/xfs/libxfs/xfs_group.c
> +++ b/fs/xfs/libxfs/xfs_group.c
> @@ -163,7 +163,8 @@ xfs_group_free(
>  
>  	xfs_defer_drain_free(&xg->xg_intents_drain);
>  #ifdef __KERNEL__
> -	kfree(xg->xg_busy_extents);
> +	if (xfs_group_has_extent_busy(xg->xg_mount, xg->xg_type))
> +		kfree(xg->xg_busy_extents);
>  #endif
>  
>  	if (uninit)
> @@ -189,9 +190,11 @@ xfs_group_insert(
>  	xg->xg_type = type;
>  
>  #ifdef __KERNEL__
> -	xg->xg_busy_extents = xfs_extent_busy_alloc();
> -	if (!xg->xg_busy_extents)
> -		return -ENOMEM;
> +	if (xfs_group_has_extent_busy(mp, type)) {
> +		xg->xg_busy_extents = xfs_extent_busy_alloc();
> +		if (!xg->xg_busy_extents)
> +			return -ENOMEM;
> +	}
>  	spin_lock_init(&xg->xg_state_lock);
>  	xfs_hooks_init(&xg->xg_rmap_update_hooks);
>  #endif
> @@ -210,7 +213,8 @@ xfs_group_insert(
>  out_drain:
>  	xfs_defer_drain_free(&xg->xg_intents_drain);
>  #ifdef __KERNEL__
> -	kfree(xg->xg_busy_extents);
> +	if (xfs_group_has_extent_busy(xg->xg_mount, xg->xg_type))
> +		kfree(xg->xg_busy_extents);
>  #endif
>  	return error;
>  }
> diff --git a/fs/xfs/xfs_extent_busy.h b/fs/xfs/xfs_extent_busy.h
> index f069b04e8ea1..3e6e019b6146 100644
> --- a/fs/xfs/xfs_extent_busy.h
> +++ b/fs/xfs/xfs_extent_busy.h
> @@ -68,4 +68,12 @@ static inline void xfs_extent_busy_sort(struct list_head *list)
>  	list_sort(NULL, list, xfs_extent_busy_ag_cmp);
>  }
>  
> +/*
> + * Zoned RTGs don't need to track busy extents, as the actual block freeing only
> + * happens by a zone reset, which forces out all transactions that touched the
> + * to be reset zone first.
> + */
> +#define xfs_group_has_extent_busy(mp, type) \
> +	((type) == XG_TYPE_AG || !xfs_has_zoned((mp)))
> +
>  #endif /* __XFS_EXTENT_BUSY_H__ */
> -- 
> 2.47.2
> 
> 

  reply	other threads:[~2025-07-16 15:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16 12:54 misc zoned allocators fixes and cleanups Christoph Hellwig
2025-07-16 12:54 ` [PATCH 1/7] xfs: don't allocate the xfs_extent_busy structure for zoned RTGs Christoph Hellwig
2025-07-16 15:50   ` Darrick J. Wong [this message]
2025-07-17  8:11   ` Carlos Maiolino
2025-07-16 12:54 ` [PATCH 2/7] xfs: use a uint32_t to cache i_used_blocks in xfs_init_zone Christoph Hellwig
2025-07-16 15:51   ` Darrick J. Wong
2025-07-16 12:54 ` [PATCH 3/7] xfs: rename oz_write_pointer to oz_allocated Christoph Hellwig
2025-07-16 15:58   ` Darrick J. Wong
2025-07-16 12:54 ` [PATCH 4/7] xfs: stop passing an inode to the zone space reservation helpers Christoph Hellwig
2025-07-16 15:59   ` Darrick J. Wong
2025-07-16 12:54 ` [PATCH 5/7] xfs: replace min & max with clamp() in xfs_max_open_zones() Christoph Hellwig
2025-07-16 16:02   ` Darrick J. Wong
2025-07-16 16:52     ` Alan Huang
2025-07-17  5:16       ` Christoph Hellwig
2025-07-17  6:42         ` Alan Huang
2025-07-16 12:54 ` [PATCH 6/7] xfs: improve the comments in xfs_max_open_zones Christoph Hellwig
2025-07-16 16:03   ` Darrick J. Wong
2025-07-16 12:54 ` [PATCH 7/7] xfs: improve the comments in xfs_select_zone_nowait Christoph Hellwig
2025-07-16 16:03   ` 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=20250716155049.GH2672049@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=hans.holmberg@wdc.com \
    --cc=hch@lst.de \
    --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;
as well as URLs for NNTP newsgroup(s).