All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Bundschuh <mkbund@amazon.com>
To: <stable@vger.kernel.org>
Cc: <sashal@kernel.org>, <linux-mm@kvack.org>, <david@kernel.org>,
	"Mark Bundschuh" <mkbund@amazon.com>
Subject: [PATCH v2 6.6 0/2] mm: replace free hugepage folios after migration
Date: Fri, 6 Nov 2026 22:08:10 +0000	[thread overview]
Message-ID: <20261106220812.2874571-1-mkbund@amazon.com> (raw)
In-Reply-To: <20261105070431.3100950-1-mkbund@amazon.com>

Full backport of 04f13d241b8b ("mm: replace free hugepage folios after
migration") with its fix 113ed54ad276.

Tested in a VM on 6.6.161: memory offline of a block with mapped huge
pages no longer livelocks, and cma_alloc() over mapped huge pages now
succeeds (it failed on 6.6.161 and with v1).

v1: https://lore.kernel.org/all/20261105070431.3100950-1-mkbund@amazon.com/

Ge Yang (1):
  mm/hugetlb: fix kernel NULL pointer dereference when replacing free
    hugetlb folios

yangge (1):
  mm: replace free hugepage folios after migration

 include/linux/hugetlb.h |  7 ++++++
 mm/hugetlb.c            | 50 +++++++++++++++++++++++++++++++++++++++++
 mm/page_alloc.c         | 12 +++++++++-
 3 files changed, 68 insertions(+), 1 deletion(-)

-- 
2.50.1



  parent reply	other threads:[~2026-11-06 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  7:04 [PATCH 6.6] mm: replace free hugepage folios after migration Mark Bundschuh
2026-11-06  7:04 ` sashiko-bot
2026-11-06 22:08 ` Mark Bundschuh [this message]
2026-11-06 22:08   ` [PATCH v2 6.6 1/2] " Mark Bundschuh
2026-11-07 22:08     ` sashiko-bot
2026-11-06 22:08   ` [PATCH v2 6.6 2/2] mm/hugetlb: fix kernel NULL pointer dereference when replacing free hugetlb folios 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=20261106220812.2874571-1-mkbund@amazon.com \
    --to=mkbund@amazon.com \
    --cc=david@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sashal@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.