From: Andrew Morton <akpm@linux-foundation.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Hugh Dickins <hughd@google.com>, Jason Gunthorpe <jgg@ziepe.ca>,
John Hubbard <jhubbard@nvidia.com>, Peter Xu <peterx@redhat.com>,
Kiryl Shutsemau <kas@kernel.org>,
Ackerley Tng <ackerleytng@google.com>,
Frank van der Linden <fvdl@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] mm/gup: fix always draining LRU caches in collect_longterm_unpinnable_folios()
Date: Thu, 6 Aug 2026 12:03:37 -0700 [thread overview]
Message-ID: <20260806120337.2c7d65fd7f9d534bf4ffed1b@linux-foundation.org> (raw)
In-Reply-To: <564e64b2-1b71-4d8e-a29e-dc98e8deb006@kernel.org>
On Thu, 6 Aug 2026 18:29:39 +0200 "David Hildenbrand (Arm)" <david@kernel.org> wrote:
> On 8/1/26 21:20, Andrew Morton wrote:
> > On Sat, 1 Aug 2026 11:49:39 -0700 (PDT) Hugh Dickins <hughd@google.com> wrote:
> >
> >>> Found by code inspection. If someone has a testcase that can easily
> >>> trigger this and result in migration problems, please test! But this
> >>> change seems to be "obvious the right thing to do".
> >>
> >> Sorry, I don't (as perhaps is too obvious). And I'm a wee bit afraid
> >> that some of the problems which those changes happened to succeed in
> >> fixing, might now reappear once the drains are finely targeted.
> >>
> >> Am I arguing for a delay before advancing to stable? Perhaps, but
> >> I think not: it's probably best to get that working as intended,
> >> then deal with any fallout if it arises: just be on guard.
> >
> > This patch is in mm-new, so it's still some months away from -stable
> > eligibility.
>
> I hope you meant weeks :)
I was unclear. The patch is (now) in mm-unstable, aimed at 7.3-rc1.
But I don't expect it to be released in -stable kernels for some time
after we've added it to 7.3-rc1.
I don't know what the latency is, really. Seems to take a week or
three for Greg to grab these things, but how much longer it takes for
it to get into the 7.2.x and earlier kernels is probably quite
variable.
> Can we get that into 7.3-rc1, though? There is quite the overlap with
> guest_memfd work, and I'll send another patch that depends on this.
Yep. In the second-week-of-merge-window batch.
next prev parent reply other threads:[~2026-08-06 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 20:27 [PATCH] mm/gup: fix always draining LRU caches in collect_longterm_unpinnable_folios() David Hildenbrand (Arm)
2026-08-01 18:49 ` Hugh Dickins
2026-08-01 19:20 ` Andrew Morton
2026-08-06 16:29 ` David Hildenbrand (Arm)
2026-08-06 19:03 ` Andrew Morton [this message]
2026-08-03 9:01 ` David Hildenbrand (Arm)
2026-08-03 9:17 ` Barry Song
2026-08-03 9:19 ` David Hildenbrand (Arm)
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=20260806120337.2c7d65fd7f9d534bf4ffed1b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ackerleytng@google.com \
--cc=david@kernel.org \
--cc=fvdl@google.com \
--cc=hughd@google.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=kas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox