From: pavrampu <pavrampu@linux.ibm.com>
To: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
David Hildenbrand <david@kernel.org>,
Muchun Song <muchun.song@linux.dev>, Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>
Subject: Re: [PATCHv2] mm/huge_memory: set the mmu_gather page size in zap_huge_pud()
Date: Fri, 30 Oct 2026 12:16:23 +0530 [thread overview]
Message-ID: <7628b0e9814084298ae09abad0b5ac6f@linux.ibm.com> (raw)
In-Reply-To: <8b853e5f9f16145859407b28af654b0f79e12642.1793318297.git.ritesh.list@gmail.com>
On 2026-10-30 05:37, Ritesh Harjani (IBM) wrote:
> Unmapping a device-dax mapping with 1G alignment on powerpc radix
> kernel
> built with CONFIG_DEBUG_VM triggers this warning on every munmap:
>
> WARNING: mm/mmu_gather.c:176 at
> __tlb_remove_folio_pages_size+0x38/0x230
> NIP [c00000000063d508] __tlb_remove_folio_pages_size+0x38/0x230
> LR [c0000000006fb688] zap_huge_pud+0x1b8/0x2d0
> Call Trace:
> zap_huge_pud+0x170/0x2d0 (unreliable)
> __zap_vma_range+0x1604/0x1e20
> unmap_vmas+0xa0/0x1f0
> unmap_region+0xb0/0x130
> vms_complete_munmap_vmas+0x120/0x310
> do_vmi_align_munmap+0x1ec/0x240
> __vm_munmap+0x148/0x220
> sys_munmap+0x28/0x40
>
> To trigger this - it is enough to mmap() /dev/dax0.0, touch the first
> byte so that the whole 1G is mapped by a single PUD and then munmap()
> it.
>
> PowerPC needs MMU_GATHER_PAGE_SIZE in which mmu_gather needs to record
> the page size for which tlb flush is needed. zap_huge_pmd(),
> zap_pte_range(), change_huge_pud() etc all do this already. However,
> since commit:
> dbe54153296d ("mm/huge_memory: add vmf_insert_folio_pud()")
>
> a device-dax PUD maps a real folio and zap_huge_pud() now hands it to
> tlb_remove_page_size(tlb, page, HPAGE_PUD_SIZE). At that point
> tlb->page_size is still whatever the previous user left behind, which
> is
> 0 for the fresh gather set up by munmap() and so the check fires.
>
> Fix this in the same way like how other similar paths do.
>
> Fixes: dbe54153296d0 ("mm/huge_memory: add vmf_insert_folio_pud()")
> Reported-by: Pavithra <pavrampu@linux.ibm.com>
> Signed-off-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
> ---
> [v1]->v2:
> =========
> - Split the 2 part patch series. Patch-1 is now superseded by a
> different patch
> from Muchun which he already posted [2].
> - No difference in this patch from v1.
>
> [v1]:
> https://lore.kernel.org/all/97f85592bb78a273be8519e6897e7f9b9bd31469.1793070429.git.ritesh.list@gmail.com/
> [2]:
> https://lore.kernel.org/all/20261029063601.1961415-1-songmuchun@bytedance.com/
>
> mm/huge_memory.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> index bd44d58e8684..7e589a2fb02d 100644
> --- a/mm/huge_memory.c
> +++ b/mm/huge_memory.c
> @@ -3040,6 +3040,8 @@ int zap_huge_pud(struct mmu_gather *tlb, struct
> vm_area_struct *vma,
> spinlock_t *ptl;
> pud_t orig_pud;
>
> + tlb_change_page_size(tlb, HPAGE_PUD_SIZE);
> +
> ptl = __pud_trans_huge_lock(pud, vma);
> if (!ptl)
> return 0;
> --
> 2.39.5
Tested on Power10 (ppc64le), kernel v7.3
Tested-by: Pavithra Prakash <pavrampu@linux.ibm.com>
next prev parent reply other threads:[~2026-10-30 6:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 0:07 Ritesh Harjani (IBM)
2026-10-30 2:11 ` Zi Yan
2026-10-30 2:21 ` Muchun Song
2026-10-30 6:46 ` pavrampu [this message]
2026-10-30 9:00 ` David Hildenbrand (Arm)
2026-10-30 10:15 ` Ritesh Harjani
2026-10-30 11:09 ` 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=7628b0e9814084298ae09abad0b5ac6f@linux.ibm.com \
--to=pavrampu@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=muchun.song@linux.dev \
--cc=ritesh.list@gmail.com \
--cc=venkat88@linux.ibm.com \
--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
all inboxes | Powered by JetHome®