From: Ren Zhijie <renzhijie2@huawei.com>
To: <ebiederm@xmission.com>, <keescook@chromium.org>,
<viro@zeniv.linux.org.uk>
Cc: <linux-mm@kvack.org>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <tanghui20@huawei.com>
Subject: [PATCH] exec: Force binary name when argv is empty
Date: Tue, 20 Sep 2022 20:08:12 +0800 [thread overview]
Message-ID: <20220920120812.231417-1-renzhijie2@huawei.com> (raw)
From: Hui Tang <tanghui20@huawei.com>
First run './execv-main execv-child', there is empty in 'COMMAND' column
when run 'ps -u'.
USER PID %CPU %MEM VSZ RSS TTY [...] TIME COMMAND
root 368 0.3 0.0 4388 764 ttyS0 0:00 ./execv-main
root 369 0.6 0.0 4520 812 ttyS0 0:00
The program 'execv-main' as follows:
int main(int argc, char **argv)
{
char *execv_argv[] = {NULL};
pid_t pid = fork();
if (pid == 0) {
execv(argv[1], execv_argv);
} else if (pid > 0) {
wait(NULL);
}
return 0;
}
So replace empty string ("") added with the name of binary
when calling execve with a NULL argv.
Fixes: dcd46d897adb ("exec: Force single empty string when argv is empty")
Signed-off-by: Hui Tang <tanghui20@huawei.com>
---
fs/exec.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/exec.c b/fs/exec.c
index 939d76e23935..7d1909a89a57 100644
--- a/fs/exec.c
+++ b/fs/exec.c
@@ -494,8 +494,8 @@ static int bprm_stack_limits(struct linux_binprm *bprm)
* signal to the parent that the child has run out of stack space.
* Instead, calculate it here so it's possible to fail gracefully.
*
- * In the case of argc = 0, make sure there is space for adding a
- * empty string (which will bump argc to 1), to ensure confused
+ * In the case of argc = 0, make sure there is space for adding
+ * bprm->filename (which will bump argc to 1), to ensure confused
* userspace programs don't start processing from argv[1], thinking
* argc can never be 0, to keep them from walking envp by accident.
* See do_execveat_common().
@@ -1900,7 +1900,7 @@ static int do_execveat_common(int fd, struct filename *filename,
retval = count(argv, MAX_ARG_STRINGS);
if (retval == 0)
- pr_warn_once("process '%s' launched '%s' with NULL argv: empty string added\n",
+ pr_warn_once("process '%s' launched '%s' with NULL argv: bprm->filename added\n",
current->comm, bprm->filename);
if (retval < 0)
goto out_free;
@@ -1929,13 +1929,13 @@ static int do_execveat_common(int fd, struct filename *filename,
goto out_free;
/*
- * When argv is empty, add an empty string ("") as argv[0] to
+ * When argv is empty, add bprm->filename as argv[0] to
* ensure confused userspace programs that start processing
* from argv[1] won't end up walking envp. See also
* bprm_stack_limits().
*/
if (bprm->argc == 0) {
- retval = copy_string_kernel("", bprm);
+ retval = copy_string_kernel(bprm->filename, bprm);
if (retval < 0)
goto out_free;
bprm->argc = 1;
--
2.17.1
next reply other threads:[~2022-09-20 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 12:08 Ren Zhijie [this message]
2022-09-20 14:42 ` Eric W. Biederman
2022-09-20 22:21 ` Kees Cook
2022-09-20 19:24 ` Al Viro
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=20220920120812.231417-1-renzhijie2@huawei.com \
--to=renzhijie2@huawei.com \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tanghui20@huawei.com \
--cc=viro@zeniv.linux.org.uk \
/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