From: Eduardo Otubo <otubo@linux.vnet.ibm.com>
To: Paul Moore <pmoore@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] seccomp: add kill() to the syscall whitelist
Date: Thu, 21 Nov 2013 14:40:48 -0200 [thread overview]
Message-ID: <528E3790.9070201@linux.vnet.ibm.com> (raw)
In-Reply-To: <20131121154015.19948.84926.stgit@localhost>
On 11/21/2013 01:40 PM, Paul Moore wrote:
> The kill() syscall is triggered with the following command:
>
> # qemu -sandbox on -monitor stdio \
> -device intel-hda -device hda-duplex -vnc :0
>
> The resulting syslog/audit message:
>
> # ausearch -m SECCOMP
> ----
> time->Wed Nov 20 09:52:08 2013
> type=SECCOMP msg=audit(1384912328.482:6656): auid=0 uid=0 gid=0 ses=854
> subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12087
> comm="qemu-kvm" sig=31 syscall=62 compat=0 ip=0x7f7a1d2abc67 code=0x0
> # scmp_sys_resolver 62
> kill
>
> Reported-by: CongLi <coli@redhat.com>
> Tested-by: CongLi <coli@redhat.com>
> Signed-off-by: Paul Moore <pmoore@redhat.com>
> ---
> qemu-seccomp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/qemu-seccomp.c b/qemu-seccomp.c
> index 69cee44..cf07869 100644
> --- a/qemu-seccomp.c
> +++ b/qemu-seccomp.c
> @@ -114,6 +114,7 @@ static const struct QemuSeccompSyscall seccomp_whitelist[] = {
> { SCMP_SYS(write), 244 },
> { SCMP_SYS(fcntl), 243 },
> { SCMP_SYS(tgkill), 242 },
> + { SCMP_SYS(kill), 242 },
> { SCMP_SYS(rt_sigaction), 242 },
> { SCMP_SYS(pipe2), 242 },
> { SCMP_SYS(munmap), 242 },
>
ACK, Reviewed and tested.
(I'll send a pull request tomorrow EOD)
Reviewed-by: Eduardo Otubo <otubo@linux.vnet.ibm.com>
--
Eduardo Otubo
IBM Linux Technology Center
next prev parent reply other threads:[~2013-11-21 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 15:40 [Qemu-devel] [PATCH] seccomp: add kill() to the syscall whitelist Paul Moore
2013-11-21 16:40 ` Eduardo Otubo [this message]
2013-11-26 15:28 ` 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=528E3790.9070201@linux.vnet.ibm.com \
--to=otubo@linux.vnet.ibm.com \
--cc=pmoore@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).