From: Yeoreum Yun <yeoreum.yun@arm.com>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Yeoreum Yun <yeoreum.yun@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@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 v3 1/2] kselftest: mm: prevent random failure of huge page split for khugepaged
Date: Fri, 28 Aug 2026 11:04:38 +0100 [thread overview]
Message-ID: <apFdNhauXl3z7nu4@e129823.arm.com> (raw)
In-Reply-To: <apFWAppcVKt4xhIT@gremlin>
Hi Lorenzo,
> > if (!rss_anon_before)
> > ksft_exit_fail_msg("No RssAnon is allocated before split\n");
> >
> > + /* Prevent khugepaged from collapsing the pages. */
> > + if (madvise(one_page, len, MADV_NOHUGEPAGE))
> > + ksft_print_msg("madvise(MADV_NOHUGEPAGE) failed\n");
>
> This should probably terminate the test no? There's no reason to expect this to
> fail and it's better to fail then to risk a flake :)
Okay. I thought it was rare, it seemed enough with just message.
I'll change with your suggesttion.
>
> > +
> > /* split all THPs */
> > write_debugfs(PID_FMT, getpid(), (uint64_t)one_page,
> > (uint64_t)one_page + len, 0);
> > @@ -227,6 +231,10 @@ static void split_pmd_thp_to_order(int order)
> > if (!check_huge_anon(one_page, 4 * pmd_pagesize, 4, pmd_pagesize))
> > ksft_exit_fail_msg("No THP is allocated\n");
> >
> > + /* Prevent khugepaged from collapsing the pages. */
> > + if (madvise(one_page, len, MADV_NOHUGEPAGE))
> > + ksft_print_msg("madvise(MADV_NOHUGEPAGE) failed\n");
> > +
>
> Same comment as above, also since this is a repeated pattern, I think it's worth
> abstracting it like:
>
> static void madv_nohuge(char *ptr, size_t len)
> {
> if (!madvise(ptr, len, MADV_NOHUGEPAGE))
> return;
>
> ksft_exit_fail_msg("MADV_NOHUGEPAGE failed, err=%d\n", errno);
> }
Acked.
>
> > /* split all THPs */
> > write_debugfs(PID_FMT, getpid(), (uint64_t)one_page,
> > (uint64_t)one_page + len, order);
> > @@ -313,6 +321,10 @@ static void split_pte_mapped_thp(void)
> > goto out;
> > }
> >
> > + /* Prevent khugepaged from collapsing the pages. */
> > + if (madvise(thp_area, thp_area_size, MADV_NOHUGEPAGE))
> > + ksft_print_msg("madvise(MADV_NOHUGEPAGE) failed\n");
> > +
> > /* Split all THPs through the remapped pages. */
> > write_debugfs(PID_FMT, getpid(), (uint64_t)page_area,
> > (uint64_t)page_area + page_area_size, 0);
> > @@ -542,6 +554,9 @@ static int create_pagecache_thp_and_fd(const char *testfile, size_t fd_size,
> > ksft_test_result_skip("Pagecache folio split skipped\n");
> > return -2;
> > }
> > + /* Prevent khugepaged from collapsing the pages. */
> > + if (madvise(*addr, fd_size, MADV_NOHUGEPAGE))
> > + ksft_print_msg("madvise(MADV_NOHUGEPAGE) failed\n");
>
> Obviously same comments re: this and above
>
Thanks!
[...]
--
Sincerely,
Yeoreum Yun
next prev parent reply other threads:[~2026-08-28 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 8:11 [PATCH v3 0/2] kselftest: mm: fix some failure of split_huge_page_test Yeoreum Yun
2026-08-28 8:11 ` [PATCH v3 1/2] kselftest: mm: prevent random failure of huge page split for khugepaged Yeoreum Yun
2026-08-28 9:39 ` Lorenzo Stoakes (ARM)
2026-08-28 10:04 ` Yeoreum Yun [this message]
2026-08-28 8:11 ` [PATCH v3 2/2] kselftest: mm: replace usage of /proc/self/smaps for check_huge_xxx() helper Yeoreum Yun
2026-08-28 9:30 ` Lorenzo Stoakes (ARM)
2026-08-28 10:17 ` Yeoreum Yun
2026-08-28 10:31 ` Lorenzo Stoakes (ARM)
2026-08-28 14:35 ` Yeoreum Yun
2026-08-28 17:21 ` Lorenzo Stoakes (ARM)
2026-08-28 15:13 ` Zi Yan
2026-08-28 15:22 ` Yeoreum Yun
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=apFdNhauXl3z7nu4@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 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®