From: Eduardo Otubo <otubo@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: pmoore@redhat.com, coreyb@linux.vnet.ibm.com
Subject: [Qemu-devel] seccomp: remove unused syscalls - for 1.6
Date: Mon, 15 Jul 2013 14:29:36 -0300 [thread overview]
Message-ID: <1373909379-21372-1-git-send-email-otubo@linux.vnet.ibm.com> (raw)
Hello all,
In this small patch series I basically:
1) Remove the ifdef's for the (not so) new libseccomp version that does a
best effort and translates x86_32 syscalls into x86_64 when possible.
2) Remove unused syscalls on the seccomp whitelist. For that removal, I've been
running several instances of Qemu using a script written on top of
virt-test[0]. After some weeks testing I could come up with this small list,
and safely remove them without breaking anything.
[0] - https://github.com/autotest/virt-test/wiki
next reply other threads:[~2013-07-15 17:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 17:29 Eduardo Otubo [this message]
2013-07-15 17:29 ` [Qemu-devel] [PATCH 1/2] seccomp: no need to check arch in syscall whitelist Eduardo Otubo
2013-07-15 18:55 ` Paul Moore
2013-07-16 17:46 ` Eduardo Otubo
2013-07-15 17:29 ` [Qemu-devel] [PATCH 2/2] seccomp: removing unused syscalls gtom whitelist Eduardo Otubo
2013-07-15 17:35 ` Eduardo Otubo
2013-07-15 20:57 ` Paolo Bonzini
2013-07-16 17:45 ` Eduardo Otubo
2013-07-16 17:49 ` Paolo Bonzini
2013-07-16 18:55 ` Eduardo Otubo
2013-07-16 19:15 ` Paolo Bonzini
2013-07-22 19:48 ` Eduardo Otubo
2013-07-15 17:29 ` [Qemu-devel] seccomp: remove unused syscalls - for 1.6 Eduardo Otubo
-- strict thread matches above, loose matches on Subject: below --
2013-07-16 18:07 Eduardo Otubo
2013-07-18 16:28 ` Anthony Liguori
2013-07-18 16:35 ` Eduardo Otubo
2013-07-18 16:37 ` Paolo Bonzini
2013-07-18 19:39 ` Paul Moore
2013-07-18 19:48 ` Peter Maydell
2013-07-18 20:05 ` Paul Moore
2013-07-18 21:31 ` Peter Maydell
2013-07-18 21:34 ` Paul Moore
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=1373909379-21372-1-git-send-email-otubo@linux.vnet.ibm.com \
--to=otubo@linux.vnet.ibm.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=pmoore@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).