From: Riku Voipio <riku.voipio@iki.fi>
To: Joel Holdsworth <joel.holdsworth@vcatechnology.com>
Cc: qemu-devel@nongnu.org, Vasileios.Kalintiris@imgtec.com,
petrosagg@resin.io
Subject: Re: [Qemu-devel] linux-user: add option to intercept execve() syscalls
Date: Mon, 30 May 2016 10:52:16 +0300 [thread overview]
Message-ID: <20160530075216.GB18068@beaming.home> (raw)
In-Reply-To: <1464192472-7885-1-git-send-email-joel.holdsworth@vcatechnology.com>
On Wed, May 25, 2016 at 05:07:48PM +0100, Joel Holdsworth wrote:
> This patch-set includes Peter Angelatos's previous patch-set [1] and
> adds code to pass arguments for setting the environment variables,
> passing the interpeter prefix, and passing the strace option.
Considering the messiness this serieas adds to QEMU, I do wonder how
much of win this avoidance really is. If you have permissions to chroot,
you generally have permissions to set binfmt_misc too. Alternatively
these kind of exec manipulations are already done by external tools like
proot and scratchbox.
However if you are ready to stay around to maintain it, and nobody else
objects the code, I can merge it.
> [1] https://patchwork.ozlabs.org/patch/582756/
>
next prev parent reply other threads:[~2016-05-30 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 16:07 [Qemu-devel] linux-user: add option to intercept execve() syscalls Joel Holdsworth
2016-05-25 16:07 ` [Qemu-devel] [PATCH 1/4] " Joel Holdsworth
2016-05-25 16:07 ` [Qemu-devel] [PATCH 2/4] linux-user: pass environment arguments in execve Joel Holdsworth
2016-05-25 16:07 ` [Qemu-devel] [PATCH 3/4] linux-user: pass elf interpreter prefix " Joel Holdsworth
2016-05-25 16:07 ` [Qemu-devel] [PATCH 4/4] linux-user: pass strace argument " Joel Holdsworth
2016-05-30 7:52 ` Riku Voipio [this message]
2016-05-31 15:59 ` [Qemu-devel] linux-user: add option to intercept execve() syscalls Joel Holdsworth
-- strict thread matches above, loose matches on Subject: below --
2016-06-14 19:26 Joel Holdsworth
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=20160530075216.GB18068@beaming.home \
--to=riku.voipio@iki.fi \
--cc=Vasileios.Kalintiris@imgtec.com \
--cc=joel.holdsworth@vcatechnology.com \
--cc=petrosagg@resin.io \
--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).