From: Andrew Morton <akpm@linux-foundation.org>
To: Brendan Jackman <jackmanb@google.com>
Cc: Vlastimil Babka <vbabka@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Alexei Starovoitov <ast@kernel.org>, Harry Yoo <harry@kernel.org>,
Shakeel Butt <shakeel.butt@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, sashiko-bot@kernel.org
Subject: Re: [PATCH 0/2] mm/page_alloc: fixes for free_pages_nolock() on RT/UP
Date: Wed, 15 Jul 2026 12:33:09 -0700 [thread overview]
Message-ID: <20260715123309.621edcb4b5ed72499d31ec9a@linux-foundation.org> (raw)
In-Reply-To: <20260715-alloc-nolock-fixes-v1-0-fadc49952dda@google.com>
On Wed, 15 Jul 2026 09:03:57 +0000 Brendan Jackman <jackmanb@google.com> wrote:
> First patch was originally part of a different series but Andrew asked
> for it to be separate:
> https://lore.kernel.org/all/20260710170311.e22bfd21c658e8357ceddeec@linux-foundation.org/
>
> Pre-existing bugs found by Sashiko during review of this other series:
> https://lore.kernel.org/all/20260703-alloc-trylock-v5-0-c87b714e19d3@google.com/
>
> I have not reproduced these bugs, and I suspect there is no real-world
> user that is affected by them.
Right, thanks. I'll stage these for the next merge window - no need to
rush these fixes into mainline.
And I staged them ahead of your "mm/page_alloc: rename FPI_TRYLOCK ->
FPI_NOLOCK", to lessen backporting hassles.
next parent reply other threads:[~2026-07-15 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260715-alloc-nolock-fixes-v1-0-fadc49952dda@google.com>
2026-07-15 19:33 ` Andrew Morton [this message]
[not found] ` <20260715-alloc-nolock-fixes-v1-1-fadc49952dda@google.com>
2026-07-15 13:00 ` [PATCH 1/2] mm/page_alloc: don't spin_trylock() in NMI on UP Vlastimil Babka (SUSE)
2026-07-16 2:13 ` Harry Yoo
[not found] ` <20260715-alloc-nolock-fixes-v1-2-fadc49952dda@google.com>
2026-07-15 13:07 ` [PATCH 2/2] mm/page_alloc: don't spin_trylock() when disallowed in free_one_page() Vlastimil Babka (SUSE)
2026-07-16 2:16 ` Harry Yoo
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=20260715123309.621edcb4b5ed72499d31ec9a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=harry@kernel.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rostedt@goodmis.org \
--cc=sashiko-bot@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.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