All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <pmoore@redhat.com>
To: qemu-devel@nongnu.org, otubo@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] seccomp: add shmctl(), mlock(), and munlock() to the syscall whitelist
Date: Mon, 03 Mar 2014 15:41:54 -0500	[thread overview]
Message-ID: <1422240.VnSJ3J12An@sifl> (raw)
In-Reply-To: <20140226152501.5062.42074.stgit@localhost>

On Wednesday, February 26, 2014 10:25:01 AM Paul Moore wrote:
> Additional testing reveals that PulseAudio requires shmctl() and the
> mlock()/munlock() syscalls on some systems/configurations.  As before,
> on systems that do require these syscalls, the problem can be seen with
> the following command line:
> 
>   # qemu -monitor stdio  -sandbox on \
>          -device intel-hda -device hda-duplex
> 
> Signed-off-by: Paul Moore <pmoore@redhat.com>
> ---
>  qemu-seccomp.c |    5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/qemu-seccomp.c b/qemu-seccomp.c
> index caa926e..3db1e9b 100644
> --- a/qemu-seccomp.c
> +++ b/qemu-seccomp.c
> @@ -225,7 +225,10 @@ static const struct QemuSeccompSyscall
> seccomp_whitelist[] = { { SCMP_SYS(fchmod), 240 },
>      { SCMP_SYS(shmget), 240 },
>      { SCMP_SYS(shmat), 240 },
> -    { SCMP_SYS(shmdt), 240 }
> +    { SCMP_SYS(shmdt), 240 },
> +    { SCMP_SYS(shmctl), 240 },
> +    { SCMP_SYS(mlock), 240 },
> +    { SCMP_SYS(munlock), 240 }
>  };
> 
>  int seccomp_start(void)

Bump to bring this back the forefront of everyone's minds.  Can we get this 
merged?

-- 
paul moore
security and virtualization @ redhat

  reply	other threads:[~2014-03-03 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 15:25 [Qemu-devel] [PATCH] seccomp: add shmctl(), mlock(), and munlock() to the syscall whitelist Paul Moore
2014-03-03 20:41 ` Paul Moore [this message]
2014-03-05 14:53   ` Eduardo Otubo
2014-03-05 17:35     ` 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=1422240.VnSJ3J12An@sifl \
    --to=pmoore@redhat.com \
    --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 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.