qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Otubo <otubo@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: pmoore@redhat.com, pbonzini@redhat.com,
	coreyb@linux.vnet.ibm.com,
	Eduardo Otubo <otubo@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCHv3 0/2] seccomp: remove unused syscalls - for 1.6
Date: Mon, 22 Jul 2013 15:33:35 -0300	[thread overview]
Message-ID: <1374518017-10424-1-git-send-email-otubo@linux.vnet.ibm.com> (raw)

In this small patch series I basically:

  v3 update:
  - reincluded getrlimit(), it's used by Xen.

  v2 update:
  - set libseccomp 2.1.0 as requirement on configure script.
  - reincluded setrlimit() (used by Xen) and removed sendfile64() from
    the whitelist.

  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

Eduardo Otubo (2):
  seccomp: no need to check arch in syscall whitelist
  seccomp: removing unused syscalls gtom whitelist

 configure      |  2 +-
 qemu-seccomp.c | 17 -----------------
 2 files changed, 1 insertion(+), 18 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2013-07-22 18:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 18:33 Eduardo Otubo [this message]
2013-07-22 18:33 ` [Qemu-devel] [PATCHv3 1/2] seccomp: no need to check arch in syscall whitelist Eduardo Otubo
2013-07-22 18:33 ` [Qemu-devel] [PATCH 2/2] seccomp: removing unused syscalls gtom whitelist Eduardo Otubo
2013-07-23  7:43 ` [Qemu-devel] [PATCHv3 0/2] seccomp: remove unused syscalls - for 1.6 Paolo Bonzini
2013-07-26 20:44   ` Eduardo Otubo
2013-07-29 20:24 ` Anthony Liguori

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=1374518017-10424-1-git-send-email-otubo@linux.vnet.ibm.com \
    --to=otubo@linux.vnet.ibm.com \
    --cc=coreyb@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.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).