From: mawupeng <mawupeng1@huawei.com>
To: <akpm@linux-foundation.org>
Cc: <mawupeng1@huawei.com>, <liuye@kylinos.cn>, <hannes@cmpxchg.org>,
<mhocko@kernel.org>, <david@kernel.org>, <ljs@kernel.org>,
<hughd@google.com>, <mgorman@techsingularity.net>,
<yang@os.amperecomputing.com>, <zhangqiuhao@huawei.com>,
<wangkefeng.wang@huawei.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] mm: vmscan: fix scan overshoot and ineligible folio scanning
Date: Tue, 1 Sep 2026 11:12:37 +0800 [thread overview]
Message-ID: <ecb5978d-977e-46a6-96bf-fb993a7804ef@huawei.com> (raw)
In-Reply-To: <20260829201809.99fe79c4725413bf80510fed@linux-foundation.org>
On 周日 2026-8-30 11:18, Andrew Morton wrote:
> On Tue, 25 Aug 2026 08:59:54 +0800 mawupeng <mawupeng1@huawei.com> wrote:
>
>> Hi, maintainers
>> Kindly ping.
>
> It's been quite a while. It would be helpful to refresh/retest/resend,
> please.
Thanks, Andrew. I’ll retest it with the background (situation, end-user impact,
reproduction, A/B) folded into the cover letter and re-tested on the current -rc.
>
> While doing this, please update the changelogging to help reviewers
> understand the end-user impact of the issue.
>
> Please also give some though to whether we should backport these fixes
> into earlier kernels, with a cc:stable. Given the unusual
> circumstances which are required to hit this, I'm thinking "no", but
> feel free to disagree!
On cc:stable — I agree it doesn’t seem warranted. The conditions needed
to trigger this are unusual enough that I don’t think a backport is
justified, so I’d lean toward not adding Cc:stable. Happy to revisit if
I’m missing something.
>
prev parent reply other threads:[~2026-09-01 3:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 7:08 [PATCH 0/2] mm: vmscan: fix scan overshoot and ineligible folio scanning Wupeng Ma
2026-08-11 7:08 ` [PATCH 1/2] mm: vmscan: charge isolate overshoot against scan quota Wupeng Ma
2026-08-11 7:08 ` [PATCH 2/2] mm: vmscan: stop scanning ineligible folios after max_nr_skipped Wupeng Ma
2026-08-12 1:42 ` [PATCH 0/2] mm: vmscan: fix scan overshoot and ineligible folio scanning Andrew Morton
2026-08-12 2:29 ` mawupeng
2026-08-25 0:59 ` mawupeng
2026-08-30 3:18 ` Andrew Morton
2026-09-01 3:12 ` mawupeng [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=ecb5978d-977e-46a6-96bf-fb993a7804ef@huawei.com \
--to=mawupeng1@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=ljs@kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=yang@os.amperecomputing.com \
--cc=zhangqiuhao@huawei.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