From: Andrew Morton <akpm@linux-foundation.org>
To: Tianyang Zhang <zhangtianyang@loongson.cn>
Cc: Harry Yoo <harry.yoo@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Vlastimil Babka <vbabka@suse.cz>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>
Subject: Re: [PATCH] mm/page_alloc.c: Avoid infinite retries caused by cpuset race
Date: Tue, 22 Apr 2025 17:11:16 -0700 [thread overview]
Message-ID: <20250422171116.f3928045a13205dc1b9a46ea@linux-foundation.org> (raw)
In-Reply-To: <025e3f51-2ab5-bc58-5475-b57103169a82@loongson.cn>
On Tue, 22 Apr 2025 20:10:06 +0800 Tianyang Zhang <zhangtianyang@loongson.cn> wrote:
>
> ...
>
> >>
> >> Simultaneously starting multiple cpuset01 from LTP can quickly
> >> reproduce this issue on a multi node server when the maximum
> >> memory pressure is reached and the swap is enabled
> >>
> >> Signed-off-by: Tianyang Zhang <zhangtianyang@loongson.cn>
> >> ---
> > What commit does it fix and should it be backported to -stable?
> >
> > There's a new 'MEMORY MANAGEMENT - PAGE ALLOCATOR' entry (only in
> > Andrew's mm.git repository now).
> >
> > Let's Cc the page allocator folks here!
>
> We first identified this issue in 6.6.52-stable , and through root cause
> analysis,
>
> it appears the problem may have existed for a significant period.
>
> However It is recommended that the fix should be backported to at least
> Linux kernel versions after 6.6-stable
OK, thanks,
This has been in mm-hotfixes-unstable for six days. Hopefully we'll
see some review activity soon (please).
next prev parent reply other threads:[~2025-04-23 0:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 8:24 Tianyang Zhang
2025-04-21 10:00 ` Harry Yoo
2025-04-21 20:28 ` Suren Baghdasaryan
2025-04-23 2:38 ` Tianyang Zhang
2025-04-23 15:35 ` Suren Baghdasaryan
2025-05-14 7:15 ` Vlastimil Babka
2025-04-22 12:10 ` Tianyang Zhang
2025-04-23 0:11 ` Andrew Morton [this message]
2025-04-23 0:22 ` Suren Baghdasaryan
2025-05-11 3:07 ` Andrew Morton
2025-05-13 16:26 ` Suren Baghdasaryan
2025-05-13 19:16 ` Andrew Morton
2025-05-13 19:33 ` Suren Baghdasaryan
2025-05-14 7:34 ` Vlastimil Babka
2025-05-14 22:42 ` Andrew Morton
2025-05-15 3:19 ` Tianyang Zhang
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=20250422171116.f3928045a13205dc1b9a46ea@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=harry.yoo@oracle.com \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=zhangtianyang@loongson.cn \
--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