Re: [PATCH 0/2] mm: vmscan: fix scan overshoot and ineligible folio scanning
From: mawupeng
Date: Mon Aug 31 2026 - 23:13:59 EST
On 周日 2026-8-30 11:18, Andrew Morton wrote:
> On Tue, 25 Aug 2026 08:59:54 +0800 mawupeng <mawupeng1@xxxxxxxxxx> 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.
>