From: "David Hildenbrand (Arm)" <david@kernel.org>
To: stable@vger.kernel.org
Cc: linux-mm@kvack.org, "David Hildenbrand (Arm)" <david@kernel.org>,
Jane Chu <jane.chu@oracle.com>, Harry Yoo <harry.yoo@oracle.com>,
Oscar Salvador <osalvador@suse.de>,
David Hildenbrand <david@redhat.com>,
Jann Horn <jannh@google.com>, Liu Shixin <liushixin2@huawei.com>,
Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@surriel.com>,
Laurence Oberman <loberman@redhat.com>,
Lance Yang <lance.yang@linux.dev>
Subject: [PATCH 6.1.y 0/4] mm/hugetlb: fixes for PMD table sharing (incl. using mmu_gather)
Date: Wed, 18 Feb 2026 10:16:03 +0100 [thread overview]
Message-ID: <20260218091608.25726-1-david@kernel.org> (raw)
In-Reply-To: <2026012605-uncorrupt-yanking-4155@gregkh>
Backport of [1] for 6.1. Backport notes are in the individual patches.
The patch "mm/rmap: fix two comments related to huge_pmd_unshare()"
was already backported.
While backporting I realized that Jane's fix was not backported yet.
Tested on x86-64 with the original reproducer.
[1] https://lore.kernel.org/linux-mm/20251223214037.580860-1-david@kernel.org/
Cc: Jane Chu <jane.chu@oracle.com>,
Cc: Harry Yoo <harry.yoo@oracle.com>,
Cc: Oscar Salvador <osalvador@suse.de>,
Cc: David Hildenbrand <david@redhat.com>,
Cc: Jann Horn <jannh@google.com>,
Cc: Liu Shixin <liushixin2@huawei.com>,
Cc: Muchun Song <muchun.song@linux.dev>,
Cc: Andrew Morton <akpm@linux-foundation.org>,
Cc: Rik van Riel <riel@surriel.com>
Cc: Laurence Oberman <loberman@redhat.com>
Cc: Lance Yang <lance.yang@linux.dev>
Cc: Liu Shixin <liushixin2@huawei.com>
David Hildenbrand (Red Hat) (3):
mm/hugetlb: fix hugetlb_pmd_shared()
mm/hugetlb: fix two comments related to huge_pmd_unshare()
mm/hugetlb: fix excessive IPI broadcasts when unsharing PMD tables
using mmu_gather
Jane Chu (1):
mm/hugetlb: fix copy_hugetlb_page_range() to use ->pt_share_count
include/asm-generic/tlb.h | 77 +++++++++++++++++++-
include/linux/hugetlb.h | 17 +++--
include/linux/mm_types.h | 1 +
mm/hugetlb.c | 143 ++++++++++++++++++++------------------
mm/mmu_gather.c | 33 +++++++++
mm/rmap.c | 25 ++++---
6 files changed, 212 insertions(+), 84 deletions(-)
--
2.43.0
next prev parent reply other threads:[~2026-02-18 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 13:19 FAILED: patch "[PATCH] mm/hugetlb: fix excessive IPI broadcasts when unsharing PMD" failed to apply to 6.1-stable tree gregkh
2026-02-18 9:16 ` David Hildenbrand (Arm) [this message]
2026-02-18 9:16 ` [PATCH 6.1.y 1/4] mm/hugetlb: fix copy_hugetlb_page_range() to use ->pt_share_count David Hildenbrand (Arm)
2026-02-18 9:16 ` [PATCH 6.1.y 2/4] mm/hugetlb: fix hugetlb_pmd_shared() David Hildenbrand (Arm)
2026-02-18 9:16 ` [PATCH 6.1.y 3/4] mm/hugetlb: fix two comments related to huge_pmd_unshare() David Hildenbrand (Arm)
2026-02-18 9:16 ` [PATCH 6.1.y 4/4] mm/hugetlb: fix excessive IPI broadcasts when unsharing PMD tables using mmu_gather 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=20260218091608.25726-1-david@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=harry.yoo@oracle.com \
--cc=jane.chu@oracle.com \
--cc=jannh@google.com \
--cc=lance.yang@linux.dev \
--cc=linux-mm@kvack.org \
--cc=liushixin2@huawei.com \
--cc=loberman@redhat.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=riel@surriel.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 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.