From: David Hildenbrand <david@redhat.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>
Cc: kernel@collabora.com, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: pagemap_scan ioctl: add PFN ZERO test cases
Date: Tue, 1 Jul 2025 16:51:29 +0200 [thread overview]
Message-ID: <20027e0c-f43b-4d10-a4d6-41dcc38145bd@redhat.com> (raw)
In-Reply-To: <20250630102443.137809-1-usama.anjum@collabora.com>
On 30.06.25 12:24, Muhammad Usama Anjum wrote:
> Add test cases to test the correctness of PFN ZERO flag of pagemap_scan
> ioctl. Test with normal pages backed memory and huge pages backed
> memory.
Just to verify: would this trigger on kernels before my fix?
>
> Cc: David Hildenbrand <david@redhat.com>
> Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> ---
> The bug has been fixed [1].
>
> [1] https://lore.kernel.org/all/20250617143532.2375383-1-david@redhat.com
> ---
> tools/testing/selftests/mm/pagemap_ioctl.c | 57 +++++++++++++++++++++-
> 1 file changed, 56 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/mm/pagemap_ioctl.c b/tools/testing/selftests/mm/pagemap_ioctl.c
> index 57b4bba2b45f3..6138de0087edf 100644
> --- a/tools/testing/selftests/mm/pagemap_ioctl.c
> +++ b/tools/testing/selftests/mm/pagemap_ioctl.c
> @@ -1,4 +1,5 @@
> // SPDX-License-Identifier: GPL-2.0
> +
> #define _GNU_SOURCE
> #include <stdio.h>
> #include <fcntl.h>
> @@ -1480,6 +1481,57 @@ static void transact_test(int page_size)
> extra_thread_faults);
> }
>
> +void zeropfn_tests(void)
> +{
> + unsigned long long mem_size;
> + struct page_region vec;
> + int i, ret;
> + char *mem;
> +
> + /* Test with page backed memory */
What is "page backed memory" ? :)
> + mem_size = 10 * page_size;
> + mem = mmap(NULL, mem_size, PROT_READ, MAP_PRIVATE | MAP_ANON, -1, 0);
> + if (mem == MAP_FAILED)
> + ksft_exit_fail_msg("error nomem\n");
> +
> + /* Touch each page to ensure it's mapped */
> + for (i = 0; i < mem_size; i += page_size)
> + (void)((volatile char *)mem)[i];
> +
> + ret = pagemap_ioctl(mem, mem_size, &vec, 1, 0,
> + (mem_size / page_size), PAGE_IS_PFNZERO, 0, 0, PAGE_IS_PFNZERO);
> + if (ret < 0)
> + ksft_exit_fail_msg("error %d %d %s\n", ret, errno, strerror(errno));
> +
> + ksft_test_result(ret == 1 && LEN(vec) == (mem_size / page_size),
> + "%s all pages must have PFNZERO set\n", __func__);
> +
> + munmap(mem, mem_size);
> +
> + /* Test with huge page */
> + mem_size = 10 * hpage_size;
> + mem = memalign(hpage_size, mem_size);
> + if (!mem)
> + ksft_exit_fail_msg("error nomem\n");
> +
> + ret = madvise(mem, mem_size, MADV_HUGEPAGE);
> + if (ret)
> + ksft_exit_fail_msg("madvise failed %d %s\n", errno, strerror(errno));
Might fail on older kernels, so we usually treat this as a skip.
> +
> + for (i = 0; i < mem_size; i += hpage_size)
> + (void)((volatile char *)mem)[i];
> +
> + ret = pagemap_ioctl(mem, mem_size, &vec, 1, 0,
> + (mem_size / page_size), PAGE_IS_PFNZERO, 0, 0, PAGE_IS_PFNZERO);
> + if (ret < 0)
> + ksft_exit_fail_msg("error %d %d %s\n", ret, errno, strerror(errno));
> +
> + ksft_test_result(ret == 1 && LEN(vec) == (mem_size / page_size),
> + "%s all huge pages must have PFNZERO set\n", __func__);
Wouldn't this be able to fail if
/sys/kernel/mm/transparent_hugepage/use_zero_page is set to false, or if
mmap() gave us a suboptimally-aligned range?
You'd have to read each and every page to get the ordinary shared
zeropage in these configs instead without making the test too complicated.
> +
> + free(mem);
Shouldn't this be an munmap() ?
> +}
> +
> int main(int __attribute__((unused)) argc, char *argv[])
> {
> int shmid, buf_size, fd, i, ret;
> @@ -1494,7 +1546,7 @@ int main(int __attribute__((unused)) argc, char *argv[])
> if (init_uffd())
> ksft_exit_pass();
>
> - ksft_set_plan(115);
> + ksft_set_plan(117);
We should probably look into converting this test to kselftest_harness.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-07-01 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 10:24 Muhammad Usama Anjum
2025-07-01 14:51 ` David Hildenbrand [this message]
2025-07-02 7:39 ` Muhammad Usama Anjum
2025-07-02 8:28 ` David Hildenbrand
2025-07-02 13:52 ` Muhammad Usama Anjum
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=20027e0c-f43b-4d10-a4d6-41dcc38145bd@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.org \
--cc=usama.anjum@collabora.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