From: Thomas Huth <thuth@redhat.com>
To: Eduardo Otubo <otubo@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv6 2/5] seccomp: add obsolete argument to command line
Date: Fri, 8 Sep 2017 15:10:55 +0200 [thread overview]
Message-ID: <43a508ee-b3c8-bc0f-e29f-892bbfa44308@redhat.com> (raw)
In-Reply-To: <20170908114407.25906-3-otubo@redhat.com>
On 08.09.2017 13:44, Eduardo Otubo wrote:
> This patch introduces the argument [,obsolete=allow] to the `-sandbox on'
> option. It allows Qemu to run safely on old system that still relies on
> old system calls.
>
> Signed-off-by: Eduardo Otubo <otubo@redhat.com>
> ---
> include/sysemu/seccomp.h | 3 ++-
> qemu-options.hx | 12 ++++++++++--
> qemu-seccomp.c | 19 ++++++++++++++++++-
> vl.c | 23 ++++++++++++++++++++++-
> 4 files changed, 52 insertions(+), 5 deletions(-)
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2017-09-08 13:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 11:44 [Qemu-devel] [PATCHv6 0/6] seccomp: feature refactoring Eduardo Otubo
2017-09-08 11:44 ` [Qemu-devel] [PATCHv6 1/5] seccomp: changing from whitelist to blacklist Eduardo Otubo
2017-09-08 13:07 ` Thomas Huth
2017-09-14 15:49 ` Daniel P. Berrange
2017-09-08 11:44 ` [Qemu-devel] [PATCHv6 2/5] seccomp: add obsolete argument to command line Eduardo Otubo
2017-09-08 13:10 ` Thomas Huth [this message]
2017-09-14 15:50 ` Daniel P. Berrange
2017-09-08 11:44 ` [Qemu-devel] [PATCHv6 3/5] seccomp: add elevateprivileges " Eduardo Otubo
2017-09-08 13:12 ` Thomas Huth
2017-09-14 15:51 ` Daniel P. Berrange
2017-09-08 11:44 ` [Qemu-devel] [PATCHv6 4/5] seccomp: add spawn " Eduardo Otubo
2017-09-08 13:13 ` Thomas Huth
2017-09-14 15:51 ` Daniel P. Berrange
2017-09-08 11:44 ` [Qemu-devel] [PATCHv6 5/5] seccomp: add resourcecontrol " Eduardo Otubo
2017-09-08 13:15 ` Thomas Huth
2017-09-14 15:51 ` Daniel P. Berrange
2017-09-14 15:32 ` [Qemu-devel] [PATCHv6 0/6] seccomp: feature refactoring Eduardo Otubo
2017-09-14 15:52 ` Daniel P. Berrange
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=43a508ee-b3c8-bc0f-e29f-892bbfa44308@redhat.com \
--to=thuth@redhat.com \
--cc=otubo@redhat.com \
--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).