From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
dipietro.salvatore@gmail.com,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org, Salvatore Dipietro <dipiets@amazon.it>
Subject: Re: [PATCH 6.18.y 0/3] mm/page_alloc: fix iomap buffered write regression from 5d8edfb900d5
Date: Sat, 14 Nov 2026 12:42:22 -0500 [thread overview]
Message-ID: <draft-agent5-0011-re-page-alloc-iomap-618@kernel.org> (raw)
In-Reply-To: <20261113110259.2901456-1-dipiets@amazon.it>
On 2026-11-13, Salvatore Dipietro <dipiets@amazon.it> wrote:
> Patches 1-2 are its prerequisites from the same mainline merge (Cc:
> stable), only moved from mm/page_alloc.h to mm/internal.h.
6ee3d87b9408 ("mm: page_alloc: do not give all non-blocking requests reserve
access") is now queued for 6.18, 6.12, 6.6, 6.1 and 5.15 from a separate
backport, so you can leave it out. A v2 only needs fe21f930d1e6 ("mm:
page_alloc: remove ALLOC_NON_BLOCK from ALLOC_RESERVES") and 0e05a469c294
("mm/page_alloc: avoid direct reclaim and compaction for costly __GFP_NORETRY
allocations"), with your Signed-off-by on both.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-14 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 11:02 [PATCH 6.18.y 0/3] mm/page_alloc: fix iomap buffered write regression from 5d8edfb900d5 Salvatore Dipietro
2026-11-13 11:02 ` [PATCH 6.18.y 1/3] mm: page_alloc: do not give all non-blocking requests reserve access Salvatore Dipietro
2026-11-13 11:02 ` [PATCH 6.18.y 2/3] mm: page_alloc: remove ALLOC_NON_BLOCK from ALLOC_RESERVES Salvatore Dipietro
2026-11-13 11:02 ` [PATCH 6.18.y 3/3] mm/page_alloc: avoid direct reclaim and compaction for costly __GFP_NORETRY allocations Salvatore Dipietro
2026-11-14 11:03 ` sashiko-bot
2026-11-13 19:09 ` [PATCH 6.18.y 0/3] mm/page_alloc: fix iomap buffered write regression from 5d8edfb900d5 Sasha Levin
2026-11-14 17:42 ` Sasha Levin [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=draft-agent5-0011-re-page-alloc-iomap-618@kernel.org \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dipietro.salvatore@gmail.com \
--cc=dipiets@amazon.it \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.org \
--cc=vbabka@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.