From: Shardul Bankar <shardul.b@mpiricsoftware.com>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>,
willy@infradead.org, akpm@linux-foundation.org,
linux-mm@kvack.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
dev.jain@arm.com, janak@mpiricsoftware.com,
shardulsb08@gmail.com
Subject: Re: [PATCH v4] lib: xarray: free unused spare node in xas_create_range()
Date: Fri, 05 Dec 2025 16:21:13 +0530 [thread overview]
Message-ID: <edc1773d7d2e36682f607549a1f69b1bc503f72e.camel@mpiricsoftware.com> (raw)
In-Reply-To: <d651e943-99f5-431e-a67d-e4e6784e720e@kernel.org>
On Fri, 2025-12-05 at 08:22 +0100, David Hildenbrand (Red Hat) wrote:
> > Link:
> > https://syzkaller.appspot.com/bug?id=a274d65fc733448ed518ad15481ed575669dd98c
> ...
> Reviewed-by: David Hildenbrand (Red Hat) <david@kernel.org>
>
>
> BTW, do we have a way to test this in a test case?
Hi David,
Thanks for the review and the Reviewed-by.
Regarding a test case: I don’t have a focused selftest or fault-
injection setup yet that reliably hits this xas_nomem() +
xas_create_range() corner case.
I noticed this spare-node leak while analyzing the Syzbot report I
referenced in the Link: tag, but the reproducer I see there doesn’t
isolate this path and reports other kmemleaks.
For now I’d prefer to treat this as a small correctness fix in xarray
itself. If I manage to come up with a robust way to exercise this path
in a selftest (e.g. via targeted fault injection in lib/test_xarray.c),
I can follow up with a separate patch, but I don’t have anything solid
to propose today.
>
>
> A follow-up cleanup that avoids labels could be something like
> (untested):
>
>
> diff --git a/lib/xarray.c b/lib/xarray.c
> index 9a8b4916540cf..325f264530fb2 100644
> --- a/lib/xarray.c
> +++ b/lib/xarray.c
> @@ -714,6 +714,7 @@ void xas_create_range(struct xa_state *xas)
> unsigned long index = xas->xa_index;
> unsigned char shift = xas->xa_shift;
> unsigned char sibs = xas->xa_sibs;
> + bool success = false;
>
> xas->xa_index |= ((sibs + 1UL) << shift) - 1;
> if (xas_is_node(xas) && xas->xa_node->shift == xas-
> >xa_shift)
> @@ -724,9 +725,11 @@ void xas_create_range(struct xa_state *xas)
> for (;;) {
> xas_create(xas, true);
> if (xas_error(xas))
> - goto restore;
> - if (xas->xa_index <= (index | XA_CHUNK_MASK))
> - goto success;
> + break
> + if (xas->xa_index <= (index | XA_CHUNK_MASK)) {
> + succeess = true;
> + break;
> + }
> xas->xa_index -= XA_CHUNK_SIZE;
>
> for (;;) {
> @@ -740,15 +743,17 @@ void xas_create_range(struct xa_state *xas)
> }
> }
>
> -restore:
> - xas->xa_shift = shift;
> - xas->xa_sibs = sibs;
> - xas->xa_index = index;
> - return;
> -success:
> - xas->xa_index = index;
> - if (xas->xa_node)
> - xas_set_offset(xas);
> + if (success) {
> + xas->xa_index = index;
> + if (xas->xa_node)
> + xas_set_offset(xas);
> + } else {
> + xas->xa_shift = shift;
> + xas->xa_sibs = sibs;
> + xas->xa_index = index;
> + }
> + /* Free any unused spare node from xas_nomem() */
> + xas_destroy(xas);
> }
> EXPORT_SYMBOL_GPL(xas_create_range);
>
>
Your bool-based version reads nicer; I’m happy to follow up with a
small cleanup patch on top that switches xas_create_range() over to
that style (with a Suggested-by tag).
Thanks and Regards,
Shardul
prev parent reply other threads:[~2025-12-05 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 14:26 Shardul Bankar
2025-12-05 7:22 ` David Hildenbrand (Red Hat)
2025-12-05 10:51 ` Shardul Bankar [this message]
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=edc1773d7d2e36682f607549a1f69b1bc503f72e.camel@mpiricsoftware.com \
--to=shardul.b@mpiricsoftware.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=janak@mpiricsoftware.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shardulsb08@gmail.com \
--cc=willy@infradead.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