From: David Hildenbrand <david@redhat.com>
To: stable@vger.kernel.org
Cc: linux-mm@kvack.org, "David Hildenbrand" <david@redhat.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Baolin Wang" <baolin.wang@linux.alibaba.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
"John Hubbard" <jhubbard@nvidia.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Kefeng Wang" <wangkefeng.wang@huawei.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
"Vishal Moola (Oracle)" <vishal.moola@gmail.com>,
"Zi Yan" <ziy@nvidia.com>
Subject: [PATCH 6.1.y 0/2] mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize()
Date: Thu, 25 Sep 2025 10:23:41 +0200 [thread overview]
Message-ID: <20250925082343.3771875-1-david@redhat.com> (raw)
In-Reply-To: <2025022402-footprint-usher-aa6e@gregkh>
Just got reminded that I never did these backports.
Patch #1 is a clean cherry pick to make the fix in patch #2 easier to
backport. One minor context conflict.
David Hildenbrand (1):
mm/migrate_device: don't add folio to be freed to LRU in
migrate_device_finalize()
Kefeng Wang (1):
mm: migrate_device: use more folio in migrate_device_finalize()
mm/migrate_device.c | 42 ++++++++++++++++++++----------------------
1 file changed, 20 insertions(+), 22 deletions(-)
base-commit: 363a599da6d9d9aaeea97fceff615580e845c72b
--
2.51.0
next parent reply other threads:[~2025-09-25 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025022402-footprint-usher-aa6e@gregkh>
2025-09-25 8:23 ` David Hildenbrand [this message]
2025-09-25 8:23 ` [PATCH 6.1.y 1/2] mm: migrate_device: use more folio " David Hildenbrand
2025-09-25 8:23 ` [PATCH 6.1.y 2/2] mm/migrate_device: don't add folio to be freed to LRU " David Hildenbrand
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=20250925082343.3771875-1-david@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.org \
--cc=vishal.moola@gmail.com \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--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