Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Cc: linux-mm@kvack.org, yangge <yangge1116@126.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Barry Song <21cnbao@gmail.com>, SeongJae Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mark Bundschuh <mkbund@amazon.com>
Subject: Re: [PATCH 5.10] mm: replace free hugepage folios after migration
Date: Thu, 5 Nov 2026 20:45:04 +0100	[thread overview]
Message-ID: <ac54a9f6-e21d-4f03-88dc-6562afd59cf6@kernel.org> (raw)
In-Reply-To: <2026-11-05-1-daily-reply-0010-mm-hugepage-folios@kernel.org>

On 11/5/26 19:39, Sasha Levin wrote:
>> [ Upstream commit 04f13d241b8b146b23038bffd907cb8278391d07 ]
> 
> These carry only the is_migrate_isolate_page() hunk of 04f13d241b8b ("mm:
> replace free hugepage folios after migration"), which has no Cc: stable or
> Fixes: tag upstream.
> 
> I need an ack from an mm maintainer (David or Andrew) on the reduced backport
> before queueing it for 5.10, 5.15, 6.1, 6.6 and 6.12.
> 

Looks alright, the other hunks are only relevant for migration support of
hugetlb folios in alloc_contig_range(), which we didn't have in 5.10 IIUC.

Acked-by: David Hildenbrand (Arm) <david@kernel.org>

-- 
Cheers,

David

  reply	other threads:[~2026-11-05 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  7:01 [PATCH 5.10] mm: replace free hugepage folios after migration Mark Bundschuh
2026-11-05 18:39 ` Sasha Levin
2026-11-05 19:45   ` David Hildenbrand (Arm) [this message]
2026-11-06 16:35 ` Sasha Levin
2026-11-06 17:58   ` Mark Bundschuh

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=ac54a9f6-e21d-4f03-88dc-6562afd59cf6@kernel.org \
    --to=david@kernel.org \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=linux-mm@kvack.org \
    --cc=mkbund@amazon.com \
    --cc=sashal@kernel.org \
    --cc=sj@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yangge1116@126.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