From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Kees Cook <keescook@chromium.org>,
Eric Biederman <ebiederm@xmission.com>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Shuah Khan <shuah@kernel.org>, Mark Brown <broonie@kernel.org>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] selftests/exec: execveat: Improve debug reporting
Date: Thu, 14 Mar 2024 13:54:50 +0500 [thread overview]
Message-ID: <1dd87e89-2306-4669-844f-ffe9e56523b6@collabora.com> (raw)
In-Reply-To: <20240313185606.work.073-kees@kernel.org>
On 3/13/24 11:56 PM, Kees Cook wrote:
> Children processes were reporting their status, duplicating the
> parent's. Remove that, and add some additional details about the test
> execution.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> Cc: Eric Biederman <ebiederm@xmission.com>
> Cc: Shuah Khan <shuah@kernel.org>
> Cc: Mark Brown <broonie@kernel.org>
> Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>
> Cc: linux-mm@kvack.org
> Cc: linux-kselftest@vger.kernel.org
Reviewed-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> ---
> tools/testing/selftests/exec/execveat.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/tools/testing/selftests/exec/execveat.c b/tools/testing/selftests/exec/execveat.c
> index 0546ca24f2b2..6418ded40bdd 100644
> --- a/tools/testing/selftests/exec/execveat.c
> +++ b/tools/testing/selftests/exec/execveat.c
> @@ -98,10 +98,9 @@ static int check_execveat_invoked_rc(int fd, const char *path, int flags,
> if (child == 0) {
> /* Child: do execveat(). */
> rc = execveat_(fd, path, argv, envp, flags);
> - ksft_print_msg("execveat() failed, rc=%d errno=%d (%s)\n",
> + ksft_print_msg("child execveat() failed, rc=%d errno=%d (%s)\n",
> rc, errno, strerror(errno));
> - ksft_test_result_fail("%s\n", test_name);
> - exit(1); /* should not reach here */
> + exit(errno);
> }
> /* Parent: wait for & check child's exit status. */
> rc = waitpid(child, &status, 0);
> @@ -226,11 +225,14 @@ static int check_execveat_pathmax(int root_dfd, const char *src, int is_script)
> * "If the command name is found, but it is not an executable utility,
> * the exit status shall be 126."), so allow either.
> */
> - if (is_script)
> + if (is_script) {
> + ksft_print_msg("Invoke script via root_dfd and relative filename\n");
> fail += check_execveat_invoked_rc(root_dfd, longpath + 1, 0,
> 127, 126);
> - else
> + } else {
> + ksft_print_msg("Invoke exec via root_dfd and relative filename\n");
> fail += check_execveat(root_dfd, longpath + 1, 0);
> + }
>
> return fail;
> }
--
BR,
Muhammad Usama Anjum
next prev parent reply other threads:[~2024-03-14 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 18:56 Kees Cook
2024-03-14 8:54 ` Muhammad Usama Anjum [this message]
2024-03-26 20:46 ` Shuah Khan
2024-03-26 22:40 ` Kees Cook
2024-03-27 16:19 ` Shuah Khan
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=1dd87e89-2306-4669-844f-ffe9e56523b6@collabora.com \
--to=usama.anjum@collabora.com \
--cc=broonie@kernel.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.org \
/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