linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shardul B <shardul.b@mpiricsoftware.com>
To: <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>, <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: Mon, 26 Jan 2026 11:16:08 +0530	[thread overview]
Message-ID: <19bf8d68cdb.ae2c0d37126486.8380742359510867201@mpiricsoftware.com> (raw)
In-Reply-To: <b2b99877afef36d9c79777846d19beeb14c81159.camel@mpiricsoftware.com>

[-- Attachment #1: Type: text/plain, Size: 437 bytes --]

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?


Thanks, Shardul

[-- Attachment #2: Type: text/html, Size: 1606 bytes --]

  reply	other threads:[~2026-01-26  5:46 UTC|newest]

Thread overview: 12+ 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
2025-12-15  2:19 ` Jinjiang Tu
2025-12-15  3:42   ` Jinjiang Tu
2025-12-31  6:29 ` Shardul Bankar
2026-01-26  5:46   ` Shardul B [this message]
2026-01-26 20:04     ` Andrew Morton
2026-01-27  1:12       ` Jinjiang Tu
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=19bf8d68cdb.ae2c0d37126486.8380742359510867201@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=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