From: "Darrick J. Wong" <djwong@kernel.org>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org, Matt Fleming <matt@readmodwrite.com>
Subject: Re: [PATCH v2 1/3] xfs: set minleft correctly for sparse chunk errortag allocation
Date: Fri, 14 Aug 2026 11:54:28 -0700 [thread overview]
Message-ID: <20260814185428.GJ3556460@frogsfrogsfrogs> (raw)
In-Reply-To: <20260814132239.271492-2-bfoster@redhat.com>
On Fri, Aug 14, 2026 at 09:22:37AM -0400, Brian Foster wrote:
> The errortag instrumentation for forced sparse chunk allocation
> jumps straight to the allocation path without setting args.minleft.
> minleft is unconditionally set to ->inobt_maxlevels for the normal
> allocation path. Lift the assignment to the initial args setup so
> it covers all possible paths.
>
> Assisted-by: LLM
> Fixes: 1cdadee11f8d ("xfs: randomly do sparse inode allocations in DEBUG mode")
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> Reviewed-by: Mark Tinguely <mark.tinguely@oracle.com>
This makes sense to me;
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> fs/xfs/libxfs/xfs_ialloc.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_ialloc.c b/fs/xfs/libxfs/xfs_ialloc.c
> index ffcdd1f691fd..633b2d6e42c5 100644
> --- a/fs/xfs/libxfs/xfs_ialloc.c
> +++ b/fs/xfs/libxfs/xfs_ialloc.c
> @@ -733,6 +733,10 @@ xfs_ialloc_ag_alloc(
> igeo->maxicount)
> return -ENOSPC;
> args.minlen = args.maxlen = igeo->ialloc_blks;
> +
> + /* Allow space for the inode btree to split. */
> + args.minleft = igeo->inobt_maxlevels;
> +
> /*
> * First try to allocate inodes contiguous with the last-allocated
> * chunk of inodes. If the filesystem is striped, this will fill
> @@ -764,8 +768,6 @@ xfs_ialloc_ag_alloc(
> args.alignment = 1;
> args.minalignslop = igeo->cluster_align - 1;
>
> - /* Allow space for the inode btree to split. */
> - args.minleft = igeo->inobt_maxlevels;
> error = xfs_alloc_vextent_exact_bno(&args,
> xfs_agbno_to_fsb(pag, args.agbno));
> if (error)
> @@ -804,10 +806,6 @@ xfs_ialloc_ag_alloc(
> * Allocate a fixed-size extent of inodes.
> */
> args.prod = 1;
> - /*
> - * Allow space for the inode btree to split.
> - */
> - args.minleft = igeo->inobt_maxlevels;
> error = xfs_alloc_vextent_near_bno(&args,
> xfs_agbno_to_fsb(pag,
> be32_to_cpu(agi->agi_root)));
> --
> 2.55.0
>
>
next prev parent reply other threads:[~2026-08-14 18:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 13:22 [PATCH v2 0/3] xfs: fix a couple sparse chunk alloc problems Brian Foster
2026-08-14 13:22 ` [PATCH v2 1/3] xfs: set minleft correctly for sparse chunk errortag allocation Brian Foster
2026-08-14 18:54 ` Darrick J. Wong [this message]
2026-08-14 13:22 ` [PATCH v2 2/3] xfs: support additional levels in the agfl minimum calculation Brian Foster
2026-08-14 18:58 ` Darrick J. Wong
2026-08-14 13:22 ` [PATCH v2 3/3] xfs: incorporate increased AGFL min requirement for minleft allocs Brian Foster
2026-08-14 13:57 ` Brian Foster
2026-08-14 14:15 ` [External] : " Mark Tinguely
2026-08-14 14:47 ` Brian Foster
2026-08-14 15:18 ` Mark Tinguely
2026-08-14 16:24 ` Brian Foster
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=20260814185428.GJ3556460@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=matt@readmodwrite.com \
/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