From: Yeoreum Yun <yeoreum.yun@arm.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Yeoreum Yun <yeoreum.yun@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>, Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R. Howlett" <liam@infradead.org>,
Nico Pache <nico.pache@linux.dev>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
Usama Arif <usama.arif@linux.dev>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Shuah Khan <shuah@kernel.org>,
Kevin Brodsky <kevin.brodsky@arm.com>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 2/3] kselftest: mm: replace usage of /proc/self/smaps for check_huge_xxx() helper
Date: Tue, 22 Sep 2026 08:00:16 +0100 [thread overview]
Message-ID: <arIngE4f82b4Jj_v@e129823.arm.com> (raw)
In-Reply-To: <f3cd3778-7423-4241-8dd5-05eb63886e65@kernel.org>
On Mon, Sep 21, 2026 at 11:05:15PM +0200, David Hildenbrand (Arm) wrote:
> On 9/21/26 20:48, Yeoreum Yun wrote:
> > Hi,
> >
> >> On 9/21/26 12:40, Yeoreum Yun wrote:
> >>> Since glibc commit 321e1fc73f (“malloc: Enable 2MB THP by default on AArch64”),
> >>> glibc may call madvise(MADV_HUGEPAGE) for sufficiently large allocations
> >>> made by memalign().
> >>>
> >>> The underlying VMA may start at a different address from the aligned
> >>> address returned by memalign(). Furthermore, a subsequent
> >>> madvise(MADV_HUGEPAGE) call does not split the VMA because the flag is
> >>> already set.
> >>>
> >>> This causes split_huge_page_test to fail because the check_huge_xxx()
> >>> helpers incorrectly require the address returned by memalign() to
> >>> match the VMA start address reported in /proc/self/smaps.
> >>>
> >>> Instead of relying on /proc/self/smaps, use /proc/self/pagemap and
> >>> /proc/kpageflags to detect huge-page mappings and large folios:
> >>>
> >>> 1. If hpage_size == pmd_pagesize, check PAGE_IS_HUGE instead of
> >>> using check_large_folios(), since only the mapping type matters.
> >>> This identifies PMD-mapped huge pages.
> >>> 2. Otherwise, use check_large_folios() to detect large folios. This
> >>> covers mTHP cases.
> >>> 3. Check the folio flags according to the type of huge page.
> >>>
> >>> Since shmem pages are also file-backed, simply check whether the page
> >>> is file-backed.
> >>>
> >>> Suggested-by: David Hildenbrand (Arm) <david@kernel.org>
> >>> Suggested-by: Zi Yan <ziy@nvidia.com>
> >>
> >> Do we need a Fixes: tag?
> >
> > Since this change is required for the chaning of behavior of glibc,
> > I don't think we don't need to add Fixes tag in here?
> >
> Our test made wrong assumptions on the underlying behavior of the user space
> allocator (no VMA merging would happen). So I'd argue that we should add a
> Fixes: for the test.
Okay. while I do
- add intermediate patch before this as you suggeeted.
- on the intermediate patch, add fix tag.
- based the patch, rebase this patch to add anon/file check for
other check_large_folios() type.
Thanks.
>
> --
> Cheers,
>
> David
--
Sincerely,
Yeoreum Yun
next prev parent reply other threads:[~2026-09-22 7:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 10:40 [PATCH v7 0/3] kselftest: mm: fix some failure of split_huge_page_test Yeoreum Yun
2026-09-21 10:40 ` [PATCH v7 1/3] kselftest: mm: prevent random failure of huge page split for khugepaged Yeoreum Yun
2026-09-21 10:40 ` [PATCH v7 2/3] kselftest: mm: replace usage of /proc/self/smaps for check_huge_xxx() helper Yeoreum Yun
2026-09-21 15:27 ` David Hildenbrand (Arm)
2026-09-21 18:48 ` Yeoreum Yun
2026-09-21 21:05 ` David Hildenbrand (Arm)
2026-09-22 7:00 ` Yeoreum Yun [this message]
2026-09-21 10:40 ` [PATCH v7 3/3] kselftest: mm: remove check_huge_shmem() Yeoreum Yun
2026-09-21 15:28 ` David Hildenbrand (Arm)
2026-09-21 15:47 ` Lorenzo Stoakes (ARM)
2026-09-22 1:31 ` Zi Yan
2026-09-23 3:11 ` Baolin Wang
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=arIngE4f82b4Jj_v@e129823.arm.com \
--to=yeoreum.yun@arm.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=kevin.brodsky@arm.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=nico.pache@linux.dev \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.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 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.