mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Shardul B <shardul.b@mpiricsoftware.com>
Cc: <willy@infradead.org>, <linux-mm@kvack.org>,
	<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<dev.jain@arm.com>, <david@kernel.org>,
	<janak@mpiricsoftware.com>, <tujinjiang@huawei.com>,
	<shardulsb08@gmail.com>
Subject: Re: [PATCH v4] lib: xarray: free unused spare node in xas_create_range()
Date: Sat, 14 Nov 2026 19:10:08 -0800	[thread overview]
Message-ID: <20261114191008.c6a23905a52c6f4f918c0d33@linux-foundation.org> (raw)
In-Reply-To: <19bf8d68cdb.ae2c0d37126486.8380742359510867201@mpiricsoftware.com>

On Mon, 26 Jan 2026 11:16:08 +0530 Shardul B <shardul.b@mpiricsoftware.com> wrote:

> Hi Matthew, Andrew,
> 
> 
> Gently pinging this patch. I’ve checked the latest linux-next (next-20260123) and the akpm-unstable branches, and it doesn't appear to have been picked up yet.
> 
> 
> The patch has a Reviewed-by from David Hildenbrand and fixes a memory leak in the XArray library identified by syzbot.
> 
> 
> If there are no further concerns, could you please let me know if this is queued for the next cycle?

I finally got onto this.  I prepared a test_array case to demonstrate
the bug and confirmed that your patch made the test happy.

I'll send the 2-patch series separately.

Thanks.

  parent reply	other threads:[~2026-11-15  3:10 UTC|newest]

Thread overview: 11+ 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)
2025-12-08  8:37 ` Dev Jain
     [not found] ` <89b96a9f-1d03-440a-93cd-2b9876be3122@huawei.com>
2025-12-15  3:42   ` Jinjiang Tu
2025-12-31  6:29 ` Shardul Bankar
     [not found]   ` <19bf8d68cdb.ae2c0d37126486.8380742359510867201@mpiricsoftware.com>
2026-01-26 20:04     ` Andrew Morton
2026-01-27  1:12       ` Jinjiang Tu
2026-11-15  3:10     ` Andrew Morton [this message]
2026-01-27  3:48   ` Matthew Wilcox

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=20261114191008.c6a23905a52c6f4f918c0d33@linux-foundation.org \
    --to=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=shardul.b@mpiricsoftware.com \
    --cc=shardulsb08@gmail.com \
    --cc=tujinjiang@huawei.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
all inboxes | Powered by JetHome®