From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Shardul Bankar <shardul.b@mpiricsoftware.com>,
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: Mon, 8 Dec 2025 12:36:42 +0100 [thread overview]
Message-ID: <ecac9bc7-d048-44cb-ae49-f380cd180e55@kernel.org> (raw)
In-Reply-To: <edc1773d7d2e36682f607549a1f69b1bc503f72e.camel@mpiricsoftware.com>
>> -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).
Yeah, feel free to send a cleanup out that removes some of these labels
(doesn't necessarily have to be what I proposed).
--
Cheers
David
next prev parent reply other threads:[~2025-12-08 11:36 UTC|newest]
Thread overview: 8+ 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
2025-12-08 11:36 ` David Hildenbrand (Red Hat) [this message]
2025-12-08 8:37 ` Dev Jain
2025-12-15 2:19 ` Jinjiang Tu
2025-12-15 3:42 ` Jinjiang Tu
2025-12-31 6:29 ` Shardul Bankar
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=ecac9bc7-d048-44cb-ae49-f380cd180e55@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.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=shardul.b@mpiricsoftware.com \
--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