From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34910) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bhJTj-0005B2-44 for qemu-devel@nongnu.org; Tue, 06 Sep 2016 12:44:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bhJTh-0006AK-VD for qemu-devel@nongnu.org; Tue, 06 Sep 2016 12:44:07 -0400 Received: from mail-wm0-x22f.google.com ([2a00:1450:400c:c09::22f]:36834) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bhJTh-0006AF-NB for qemu-devel@nongnu.org; Tue, 06 Sep 2016 12:44:05 -0400 Received: by mail-wm0-x22f.google.com with SMTP id b187so74317331wme.1 for ; Tue, 06 Sep 2016 09:44:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Eduardo Otubo Date: Tue, 06 Sep 2016 16:43:54 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] seccomp missing calls in 2.7.0? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Brian Rak , qemu-devel@nongnu.org This feature is enabled by default in virt-test/avocado and yes lots of people use it. Please send a patch and I'll merge it. On Tue, Sep 6, 2016, 18:41 Brian Rak wrote: > I've been testing out 2.7.0 with seccomp support. Whenever I connect to > the VNC console, the process gets killed by the kernel. dmesg shows: > > audit: type=1326 audit(1473175350.674:2): auid=0 uid=107 gid=107 > ses=423110 pid=32202 comm="qemu-kvm" exe="/bin/qemu-system-x86_64" > sig=31 arch=c000003e syscall=98 compat=0 ip=0x7f2beba83477 code=0x0 > > syscall 98 appears to be getrusage, which does not appear in > qemu-seccomp.c. > > Is seccomp a supported feature these days? I'm guessing it does not get > a whole lot of use. > > >