From: David Hildenbrand <david@redhat.com>
To: Donet Tom <donettom@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Ritesh Harjani <ritesh.list@gmail.com>,
Xu Xin <xu.xin16@zte.com.cn>,
Chengming Zhou <chengming.zhou@linux.dev>,
Wei Yang <richard.weiyang@gmail.com>,
Aboorva Devarajan <aboorvad@linux.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] selftests/mm: add fork inheritance test for ksm_merging_pages counter
Date: Tue, 26 Aug 2025 15:22:10 +0200 [thread overview]
Message-ID: <ba6d3e50-d8dc-4ee4-ae44-bc1b57e4a2dd@redhat.com> (raw)
In-Reply-To: <88d6d5f08ff119625fa9accaa7b849dd77f9df25.1756211338.git.donettom@linux.ibm.com>
On 26.08.25 14:49, Donet Tom wrote:
> Add a new selftest to verify whether the `ksm_merging_pages` counter
"to verify ... is *not* inherited" ?
> in `mm_struct` is inherited by a child process after fork. This helps
> ensure correctness of KSM accounting across process creation.
>
> Signed-off-by: Donet Tom <donettom@linux.ibm.com>
> ---
> .../selftests/mm/ksm_functional_tests.c | 42 ++++++++++++++++++-
> 1 file changed, 41 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/mm/ksm_functional_tests.c b/tools/testing/selftests/mm/ksm_functional_tests.c
> index 712f43c87736..d971394c9567 100644
> --- a/tools/testing/selftests/mm/ksm_functional_tests.c
> +++ b/tools/testing/selftests/mm/ksm_functional_tests.c
> @@ -602,6 +602,45 @@ static void test_prot_none(void)
> munmap(map, size);
> }
>
> +static void test_fork_ksm_merging_page(void)
> +{
> + const unsigned int size = 2 * MiB;
> + char *map;
> + pid_t child_pid;
> + int status;
> +
> + ksft_print_msg("[RUN] %s\n", __func__);
> +
> + map = mmap_and_merge_range(0xcf, size, PROT_READ | PROT_WRITE, KSM_MERGE_MADVISE);
> + if (map == MAP_FAILED)
> + return;
> +
> + child_pid = fork();
> + if (!child_pid) {
> + int mpages;
> +
> + init_global_file_handles();
> + mpages = ksm_get_self_merging_pages();
> + if (mpages > 0)
> + ksft_test_result_fail("ksm_merging_page in child: %d\n", mpages);
> +
> + exit(0);
> + } else if (child_pid < 0) {
> + ksft_test_result_fail("fork() failed\n");
> + return;
> + }
> +
> + if (waitpid(child_pid, &status, 0) < 0) {
> + ksft_test_result_fail("waitpid() failed\n");
> + return;
> + }
> +
> + ksft_test_result_pass("ksm_merging_pages is not inherited after fork\n");
Won't this trigger a fail in the child and a pass in the parent process?
You should likely instead let the child return the result (or the
number) and check that here.
--
Cheers
David / dhildenb
next prev parent reply other threads:[~2025-08-26 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 12:49 [PATCH 1/2] mm/ksm: Reset KSM counters in mm_struct during fork Donet Tom
2025-08-26 12:49 ` [PATCH 2/2] selftests/mm: add fork inheritance test for ksm_merging_pages counter Donet Tom
2025-08-26 13:22 ` David Hildenbrand [this message]
2025-08-27 18:03 ` Donet Tom
2025-08-26 13:19 ` [PATCH 1/2] mm/ksm: Reset KSM counters in mm_struct during fork David Hildenbrand
2025-08-27 18:03 ` Donet Tom
2025-08-26 13:47 ` Giorgi Tchankvetadze
2025-08-26 14:09 ` David Hildenbrand
2025-08-27 18:09 ` Donet Tom
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=ba6d3e50-d8dc-4ee4-ae44-bc1b57e4a2dd@redhat.com \
--to=david@redhat.com \
--cc=aboorvad@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=donettom@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@gmail.com \
--cc=ritesh.list@gmail.com \
--cc=xu.xin16@zte.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).