From: Shardul Bankar <shardul.b@mpiricsoftware.com>
To: Jinjiang Tu <tujinjiang@huawei.com>,
"David Hildenbrand (Red Hat)" <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
ziy@nvidia.com, lorenzo.stoakes@oracle.com,
baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
baohua@kernel.org, lance.yang@linux.dev, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>, shardulsb08@gmail.com
Subject: Re: [bug report] memory leak of xa_node in collapse_file() when rollbacks
Date: Thu, 25 Dec 2025 09:45:16 +0530 [thread overview]
Message-ID: <308b7b3c4f6c74c46906e25d6069049c70222ed8.camel@mpiricsoftware.com> (raw)
In-Reply-To: <a629d3bb-c7e2-41e0-87e0-7a7a6367c1b6@huawei.com>
On Thu, 2025-12-18 at 21:11 +0800, Jinjiang Tu wrote:
>
> 在 2025/12/18 20:49, David Hildenbrand (Red Hat) 写道:
>
> > >
> >
> > Thanks for checking. I thought that was also discussed as part of
> > the other fix.
> >
> > See [2] where we have
> >
> > "Note: This fixes the leak of pre-allocated nodes. A separate fix
> > will
> > be needed to clean up empty nodes that were inserted into the tree
> > by
> > xas_create_range() but never populated."
> >
> > Is that the issue you are describing? (sounds like it, but I only
> > skimmed over the details).
> >
> > CCing Shardul.
> Yes, the same issue. As I descirbed in the first email:
> "
> At first, I tried to destory the empty nodes when collapse_file()
> goes to rollback path. However,
> collapse_file() only holds xarray lock and may release the lock, so
> we couldn't prevent concurrent
> call of collapse_file(), so the deleted empty nodes may be needed by
> other collapse_file() calls.
> "
Hi David, Jinjiang,
As Jinjiang mentioned, this appears to address what I had originally
referred to in the "Note:" in [1].
Just to clarify the context of the "Note:", that was based on my
assumption at the time that such empty nodes would be considered leaks.
After Dev’s feedback in [2]:
"No "fix" is needed in this case, the empty nodes are there in the tree
and there is no leak."
and looking at the older discussion in [3]:
"There's nothing to free; if a node is allocated, then it's stored in
the tree where it can later be found and reused. "
my updated understanding is that there is no leak in this case- the
nodes remain valid and reusable, and therefore do not require a
separate fix.
David could you correct me if I am mistaken?
[1]
https://lore.kernel.org/linux-mm/20251123132727.3262731-1-shardul.b@mpiricsoftware.com/
[2]
https://lore.kernel.org/linux-mm/57cbf887-d181-418b-a6c7-9f3eff5d632a@arm.com/
[3]
https://lore.kernel.org/all/Ys1r06szkVi3QEai@casper.infradead.org/
Thanks,
Shardul
next prev parent reply other threads:[~2025-12-25 4:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 11:45 Jinjiang Tu
2025-12-18 11:51 ` David Hildenbrand (Red Hat)
2025-12-18 12:18 ` Jinjiang Tu
2025-12-18 12:49 ` David Hildenbrand (Red Hat)
2025-12-18 13:11 ` Jinjiang Tu
2025-12-25 4:15 ` Shardul Bankar [this message]
2025-12-27 1:24 ` Jinjiang Tu
2025-12-30 21:03 ` David Hildenbrand (Red Hat)
2025-12-31 6:29 ` Jinjiang Tu
2025-12-18 12:35 ` Jinjiang Tu
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=308b7b3c4f6c74c46906e25d6069049c70222ed8.camel@mpiricsoftware.com \
--to=shardul.b@mpiricsoftware.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=shardulsb08@gmail.com \
--cc=tujinjiang@huawei.com \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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