[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <063206d1-9f60-44b0-a8e6-77b49ba4a871@arm.com>
Date: Mon, 16 Jun 2025 21:58:38 +0530
From: Dev Jain <dev.jain@....com>
To: Aboorva Devarajan <aboorvad@...ux.ibm.com>, akpm@...ux-foundation.org,
Liam.Howlett@...cle.com, lorenzo.stoakes@...cle.com, shuah@...nel.org,
pfalcato@...e.de, david@...hat.com, ziy@...dia.com,
baolin.wang@...ux.alibaba.com, npache@...hat.com, ryan.roberts@....com,
baohua@...nel.org
Cc: linux-mm@...ck.org, linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org, donettom@...ux.ibm.com, ritesh.list@...il.com
Subject: Re: [PATCH 3/6] selftests/mm : fix test_prctl_fork_exec failure
On 16/06/25 9:36 pm, Aboorva Devarajan wrote:
> From: Donet Tom <donettom@...ux.ibm.com>
>
> execv argument is an array of pointers to null-terminated strings.
> In this patch we added NULL in the execv argument to fix the test
> failure.
Just a comment, how did this test suddenly start failing now? Also is a
fixes tag required? Clearly I am missing something.
> Signed-off-by: Donet Tom <donettom@...ux.ibm.com>
> Signed-off-by: Aboorva Devarajan <aboorvad@...ux.ibm.com>
> ---
> tools/testing/selftests/mm/ksm_functional_tests.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/mm/ksm_functional_tests.c b/tools/testing/selftests/mm/ksm_functional_tests.c
> index d7d3c22c077a..6ea50272a0ba 100644
> --- a/tools/testing/selftests/mm/ksm_functional_tests.c
> +++ b/tools/testing/selftests/mm/ksm_functional_tests.c
> @@ -579,7 +579,7 @@ static void test_prctl_fork_exec(void)
> return;
> } else if (child_pid == 0) {
> char *prg_name = "./ksm_functional_tests";
> - char *argv_for_program[] = { prg_name, FORK_EXEC_CHILD_PRG_NAME };
> + char *argv_for_program[] = { prg_name, FORK_EXEC_CHILD_PRG_NAME, NULL };
>
> execv(prg_name, argv_for_program);
> return;
Powered by blists - more mailing lists