From: dion@linutronix.de
To: qemu-devel@nongnu.org
Cc: Olivier Dion <dion@linutronix.de>, john.ogness@linutronix.de
Subject: [Qemu-devel] [PATCH 0/1] Handle /proc/self/exe in execve
Date: Wed, 7 Aug 2019 15:54:57 +0200 [thread overview]
Message-ID: <20190807135458.32440-1-dion@linutronix.de> (raw)
From: Olivier Dion <dion@linutronix.de>
When the emulated process try to execve itself through /proc/self/exe,
QEMU user will be executed instead of the process.
The following short program demonstrated that:
----------------------------------------------------------------------
#include <stdio.h>
#include <string.h>
#include <unistd.h>
static char *ARGV0 = "STOP";
static char *ARGV1 = "-this-is-not-an-option";
int main(int argc, char *argv[], char *environ[])
{
(void)argc;
if (strcmp(argv[0], ARGV0) == 0)
return 0;
argv[0] = ARGV0;
argv[1] = ARGV1;
execve("/proc/self/exe", (char **const)argv,
(char **const)environ);
perror("execve");
return 1;
}
----------------------------------------------------------------------
Will output:
----------------------------------------------------------------------
qemu: unknown option 'this-is-not-an-option'
----------------------------------------------------------------------
Olivier Dion (1):
linux-user: Handle /proc/self/exe in syscall execve
linux-user/syscall.c | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
--
2.22.0
next reply other threads:[~2019-08-07 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 13:54 dion [this message]
2019-08-07 13:54 ` [Qemu-devel] [PATCH 1/1] linux-user: Handle /proc/self/exe in syscall execve dion
2019-08-23 16:58 ` Laurent Vivier
2019-09-02 17:36 ` Olivier Dion
2019-09-02 19:02 ` Laurent Vivier
2019-09-16 15:55 ` [Qemu-devel] [PATCH v2 0/1] Handle /proc/self/exe in execve Olivier Dion
2019-09-16 15:55 ` [Qemu-devel] [PATCH v2 1/1] Handle /proc/self/exe in syscall execve Olivier Dion
2019-09-16 16:55 ` [Qemu-devel] [PATCH v2 0/1] Handle /proc/self/exe in execve no-reply
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=20190807135458.32440-1-dion@linutronix.de \
--to=dion@linutronix.de \
--cc=john.ogness@linutronix.de \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).