mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Nickolai Zeldovich <nickolai@csail.mit.edu>
Cc: Matthew Wilcox <willy@infradead.org>,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v1 0/3] ida: fix the allocation failure paths of ida_alloc_range()
Date: Mon, 12 Oct 2026 17:46:33 -0700	[thread overview]
Message-ID: <20261012174633.6a86cf6ab068f3c1eff94fb3@linux-foundation.org> (raw)
In-Reply-To: <20261013002703.773923-1-nickolai@csail.mit.edu>

On Mon, 12 Oct 2026 20:27:00 -0400 Nickolai Zeldovich <nickolai@csail.mit.edu> wrote:

> These three patches fix what ida_alloc_range() does when its xas_store()
> fails for want of a node, found while formally verifying the function
> against the kernel binary, where its resource accounting could not be
> established against the code as it is.

Please teach your LLM about the first 32 lines of
Documentation/process/stable-kernel-rules.rst.  Seriously.

Please also tell it that when fixing a bug, it should fully describe
the userspace-visible runtime effects of that bug, especially when
proposing a -stable backport.

Thanks. 

      parent reply	other threads:[~2026-10-13  0:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13  0:27 Nickolai Zeldovich
2026-10-13  0:27 ` [PATCH v1 1/3] ida: clear the bit of a bitmap that ida_alloc_range() failed to store Nickolai Zeldovich
2026-10-13  0:27 ` [PATCH v1 2/3] ida: free the bitmaps that ida_alloc_range() fails " Nickolai Zeldovich
2026-10-13  0:27 ` [PATCH v1 3/3] ida: free the preallocated node on the ida_alloc_range() failure paths Nickolai Zeldovich
2026-10-13  0:46 ` Andrew Morton [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=20261012174633.6a86cf6ab068f3c1eff94fb3@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickolai@csail.mit.edu \
    --cc=stable@vger.kernel.org \
    --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®