All of lore.kernel.org
 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
Subject: [Qemu-devel] seccomp: remove unused syscalls - for 1.6
Date: Tue, 16 Jul 2013 15:07:36 -0300	[thread overview]
Message-ID: <1373998058-20012-1-git-send-email-otubo@linux.vnet.ibm.com> (raw)

Hello all,

In this small patch series I basically:

  v2 update:
  - set libseccomp 2.1.0 as requirement on configure script.
  - removed setrlimit and added sendfile64 to 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

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16 18:07 Eduardo Otubo [this message]
2013-07-16 18:07 ` [Qemu-devel] [PATCHv2 1/2] seccomp: no need to check arch in syscall whitelist Eduardo Otubo
2013-07-16 18:07 ` [Qemu-devel] [PATCHv2 2/2] seccomp: removing unused syscalls from whitelist Eduardo Otubo
2013-07-18 16:28 ` [Qemu-devel] seccomp: remove unused syscalls - for 1.6 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
  -- strict thread matches above, loose matches on Subject: below --
2013-07-15 17:29 Eduardo Otubo
2013-07-15 17:29 ` Eduardo Otubo

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=1373998058-20012-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.