From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Corey Bryant <coreyb@linux.vnet.ibm.com>,
Eduardo Otubo <otubo@linux.vnet.ibm.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Cc: pmoore@redhat.com, qemu-devel@nongnu.org, anthony@codemonkey.ws
Subject: Re: [Qemu-devel] [PATCH] seccomp: "-sandbox on" won't kill Qemu when option not built in
Date: Tue, 10 Dec 2013 16:48:54 -0200 [thread overview]
Message-ID: <52A76216.7090303@redhat.com> (raw)
In-Reply-To: <52A68867.4080309@linux.vnet.ibm.com>
On 12/10/2013 01:20 AM, Corey Bryant wrote:
>>> IMHO the test suite should probe to see if sandbox is working or not,
>>> and
>>> just not use the "-sandbox on" arg if the host doesn't support it.
>>
>> But I think this could be done on virt-test as well :)
>>
>
> This would make sense.
>
> Although it sounds like Lucas was looking for an error message when
> seccomp kills qemu. Maybe virt-test could grep the audit log for the
> existence of a "type=SECCOMP" record within the test's time of
> execution, and issue a message based on that.
It's a valid idea. The problem I see with it is that not every distro
out there uses SELinux. Not getting into the merits of whether they
should, ideally it'd be nice to have this working on distros that won't
use SELinux.
next prev parent reply other threads:[~2013-12-10 18:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 17:20 [Qemu-devel] [PATCH] seccomp: "-sandbox on" won't kill Qemu when option not built in Eduardo Otubo
2013-12-09 17:33 ` Daniel P. Berrange
2013-12-09 17:51 ` Eduardo Otubo
2013-12-09 18:16 ` Paul Moore
2013-12-10 3:20 ` Corey Bryant
2013-12-10 18:48 ` Lucas Meneghel Rodrigues [this message]
2013-12-10 19:31 ` Paul Moore
2013-12-10 20:13 ` Lucas Meneghel Rodrigues
2013-12-10 19:35 ` Eduardo Otubo
2013-12-09 19:11 ` Lucas Meneghel Rodrigues
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=52A76216.7090303@redhat.com \
--to=lmr@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=berrange@redhat.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=otubo@linux.vnet.ibm.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 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).