On Wed, Apr 26, 2017 at 5:12 PM, Simon Déziel
<1675...@bugs.launchpad.net> wrote:
> On 2017-04-26 04:30 AM, Eduardo Otubo wrote:
>> On Tue, Apr 25, 2017 at 6:18 PM, Simon Déziel
>> <1675...@bugs.launchpad.net> wrote:
>>> On 2017-03-22 04:02 PM, Eduardo Otubo wrote:
On Wed, Mar 22, 2017 at
On 2017-04-26 04:30 AM, Eduardo Otubo wrote:
> On Tue, Apr 25, 2017 at 6:18 PM, Simon Déziel
> <1675...@bugs.launchpad.net> wrote:
>> On 2017-03-22 04:02 PM, Eduardo Otubo wrote:
>>> On Wed, Mar 22, 2017 at 07=28=12PM -, Simon Déziel wrote:
On 2017-03-22 03:08 PM, Eduardo Otubo wrote:
On Tue, Apr 25, 2017 at 6:18 PM, Simon Déziel
<1675...@bugs.launchpad.net> wrote:
> On 2017-03-22 04:02 PM, Eduardo Otubo wrote:
>> On Wed, Mar 22, 2017 at 07=28=12PM -, Simon Déziel wrote:
>>> On 2017-03-22 03:08 PM, Eduardo Otubo wrote:
These patches are intended to 2.9, but will be
On 2017-03-22 04:02 PM, Eduardo Otubo wrote:
> On Wed, Mar 22, 2017 at 07=28=12PM -, Simon Déziel wrote:
>> On 2017-03-22 03:08 PM, Eduardo Otubo wrote:
>>> These patches are intended to 2.9, but will be able to be backported.
>>> What's the urgency of this issue? Do you need a hotfix for it
On Wed, Mar 22, 2017 at 07=28=12PM -, Simon Déziel wrote:
> On 2017-03-22 03:08 PM, Eduardo Otubo wrote:
> > I'm working on a completely refactoring of the seccomp feature in qemu:
> > https://github.com/otubo/qemu/commits/seccomp-refactoring
>
> Nice. Since you are moving from whitelisting
On 2017-03-22 03:08 PM, Eduardo Otubo wrote:
> I'm working on a completely refactoring of the seccomp feature in qemu:
> https://github.com/otubo/qemu/commits/seccomp-refactoring
Nice. Since you are moving from whitelisting to blacklisting I don't
think that will be easy to backport/SRU but I'll
I'm working on a completely refactoring of the seccomp feature in qemu:
https://github.com/otubo/qemu/commits/seccomp-refactoring
These patches are intended to 2.9, but will be able to be backported.
What's the urgency of this issue? Do you need a hotfix for it directly
for 2.5 or can wait until
