qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <pmoore@redhat.com>
To: qemu-devel@nongnu.org
Cc: debfx@fobos.de, Eduardo Otubo <otubo@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PULL 00/02] seccomp: adding new syscalls to the whitelist
Date: Mon, 24 Mar 2014 14:13:05 -0400	[thread overview]
Message-ID: <3706322.7y0sYUHAod@sifl> (raw)
In-Reply-To: <1394718164-7883-1-git-send-email-otubo@linux.vnet.ibm.com>

On Thursday, March 13, 2014 10:42:42 AM Eduardo Otubo wrote:
> The following changes since commit 750036a848ea913ba6343718ffa70da98f7eef6b:
> 
>   Merge remote-tracking branch 'remotes/afaerber/tags/prep-for-upstream'
> into staging (2014-03-12 17:53:37 +0000)
> 
> are available in the git repository at:
> 
>   git://github.com/otubo/qemu.git seccomp
> 
> Felix Geyer (1):
>       seccomp: add timerfd_create and timerfd_settime to the whitelist
> 
> Paul Moore (1):
>       seccomp: add shmctl(), mlock(), and munlock() to the syscall whitelist
> 
>  qemu-seccomp.c |    7 ++++++-
>  1 files changed, 6 insertions(+), 1 deletions(-)

Notice this still hasn't made it upstream and thought I would check to see 
where things stood ...

-- 
paul moore
security and virtualization @ redhat

  parent reply	other threads:[~2014-03-24 19:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 13:42 [Qemu-devel] [PULL 00/02] seccomp: adding new syscalls to the whitelist Eduardo Otubo
2014-03-13 13:42 ` [Qemu-devel] [PULL 01/02] seccomp: add timerfd_create and timerfd_settime " Eduardo Otubo
2014-03-13 13:42 ` [Qemu-devel] [PULL 02/02] seccomp: add shmctl(), mlock(), and munlock() to the syscall whitelist Eduardo Otubo
2014-03-24 18:13 ` Paul Moore [this message]
2014-04-01 13:06   ` [Qemu-devel] [PULL 00/02] seccomp: adding new syscalls to the whitelist Eduardo Otubo
2014-04-02 15:53     ` Paolo Bonzini
2014-04-03 11:14       ` Peter Maydell

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=3706322.7y0sYUHAod@sifl \
    --to=pmoore@redhat.com \
    --cc=debfx@fobos.de \
    --cc=otubo@linux.vnet.ibm.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).