Hi,
This series was run against 'syntax-check' test by patchew.org, which failed,
please find the details below:
Type: series
Message-id: 20180830120941.22155-1-marcandre.lur...@redhat.com
Subject: [libvirt] [PATCH] qemu: clear seccomp capability if TSYNC is not
supported by host
On Thu, Aug 30, 2018 at 02:37:48PM +0200, Marc-André Lureau wrote:
> Hi
>
> On Thu, Aug 30, 2018 at 2:25 PM, Ján Tomko wrote:
> > On Thu, Aug 30, 2018 at 02:09:41PM +0200, marcandre.lur...@redhat.com wrote:
> >>
> >> From: Marc-André Lureau
> >>
> >> With qemu <= 3.0, when using "-seccomp on", t
Hi
On Thu, Aug 30, 2018 at 2:25 PM, Ján Tomko wrote:
> On Thu, Aug 30, 2018 at 02:09:41PM +0200, marcandre.lur...@redhat.com wrote:
>>
>> From: Marc-André Lureau
>>
>> With qemu <= 3.0, when using "-seccomp on", the seccomp policy is only
>> applied to the main thread, the vcpu worker thread and
On Thu, Aug 30, 2018 at 02:09:41PM +0200, marcandre.lur...@redhat.com wrote:
From: Marc-André Lureau
With qemu <= 3.0, when using "-seccomp on", the seccomp policy is only
applied to the main thread, the vcpu worker thread and other worker
threads created after seccomp policy is applied; the se
On Thu, Aug 30, 2018 at 02:09:41PM +0200, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> With qemu <= 3.0, when using "-seccomp on", the seccomp policy is only
> applied to the main thread, the vcpu worker thread and other worker
> threads created after seccomp policy is applied
From: Marc-André Lureau
With qemu <= 3.0, when using "-seccomp on", the seccomp policy is only
applied to the main thread, the vcpu worker thread and other worker
threads created after seccomp policy is applied; the seccomp policy is
not applied to e.g. the RCU thread because it is created before
