public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] syscalls/execve06: Add test for argv[0] = NULL
Date: Tue, 14 Jun 2022 15:04:20 +0200	[thread overview]
Message-ID: <YqiHVJhvhf16s2kL@yuki> (raw)
In-Reply-To: <YqdKVngCCGUfFDCZ@pevik>

Hi!
> I wonder why this does not work:
> 	.needs_cmds = (const char *[]) {
> 		"execve06_child",
> 		NULL
> 	},
>
> tst_test.c:1526: TINFO: Timeout per run is 0h 00m 30s
> execve06.c:33: TFAIL: Failed to execute execl01_child: ENOENT (2)
> tst_test.c:395: TBROK: Invalid child (23451) exit value 1

The difference is because the test library adds current directory and
test start directory into $PATH before a test is executed, see
add_paths() in the tst_test.c.

The .needs_cmds is for binaries installed on the system in /usr/bin/
etc. so it does not make much sense to call the add_paths() before we
process the array.

> > +
> > +	pid = SAFE_FORK();
> > +	if (pid == 0) {
> > +		execve(path, argv, envp);
> > +		tst_brk(TFAIL | TERRNO, "Failed to execute execl01_child");
> > +	}
> > +}
> > +
> > +static struct tst_test test = {
> > +	.forks_child = 1,
> > +	.child_needs_reinit = 1,
> > +	.test_all = verify_execve,
> > +	.tags = (const struct tst_tag[]) {
> > +		{"linux-git", "dcd46d897adb"},
> > +		{"CVE", "2021-4034"},
> > +		{}
> > +	}
> > +};
> > diff --git a/testcases/kernel/syscalls/execve/execve06_child.c b/testcases/kernel/syscalls/execve/execve06_child.c
> > new file mode 100644
> > index 000000000..17280d58a
> > --- /dev/null
> > +++ b/testcases/kernel/syscalls/execve/execve06_child.c
> > @@ -0,0 +1,27 @@
> > +// SPDX-License-Identifier: GPL-2.0-or-later
> > +/*
> > + * Copyright (C) 2022 Cyril Hrubis chrubis@suse.cz
> very nit: <chrubis@suse.cz> (missing < >)

Will fix.

> > + */
> > +
> > +#define TST_NO_DEFAULT_MAIN
> > +#include <stdlib.h>
> > +#include "tst_test.h"
> > +
> > +int main(int argc, char *argv[])
> > +{
> > +	tst_reinit();
> > +
> > +	if (argc != 1) {
> > +		tst_res(TFAIL, "argc is %d, expected 1", argc);
> > +		return 0;
> > +	}
> > +
> > +	if (!argv[0]) {
> > +		tst_res(TFAIL, "argv[0] == NULL");
> > +		return 0;
> > +	}
> > +
> > +	tst_res(TPASS, "argv[0] was filled in by kernel");
> 
> Testing matches the description from kernel commit.
> Maybe also test for argv[0] being empty string (to make sure behavior does not
> change, although unlikely it'd change)?

It should be safe either way but I decided to be less specific and only
check that something have been added there.

> I tested it on various kernels, works as expected.
> 
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
> Tested-by: Petr Vorel <pvorel@suse.cz>

I will push it with the added runtest entries and fixed copyright then.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-06-14 13:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 12:51 [LTP] [PATCH] syscalls/execve06: Add test for argv[0] = NULL Cyril Hrubis
2022-06-13 13:51 ` Petr Vorel
2022-06-14 12:17   ` Cyril Hrubis
2022-06-13 14:31 ` Petr Vorel
2022-06-14 13:04   ` Cyril Hrubis [this message]
2022-06-14 13:34     ` Petr Vorel

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=YqiHVJhvhf16s2kL@yuki \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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