On 2017-03-22 04:02 PM, Eduardo Otubo wrote:
> On Wed, Mar 22, 2017 at 07=28=12PM -0000, 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 directly
>>> for 2.5 or can wait until my refactoring hits 2.9?
>>
>> There is no rush since we've been waiting since Trusty/2.0 already :)
>> We'll start our new Xenial/2.5 cluster without sandbox and we'll revisit
>> this once a SRU lands in Xenial. Please don't hesitate to ask me to test
>> something if that can help. Thanks for the prompt reply!
> 
> Sure! I'll have you on CC whenever I post my v2 patches on the mailing
> list so you can also keep track of this issue there. My plan is to
> release it mid next week.

Hi Eduardo,

I don't know if you had time to make some progress on that but if you
have an updated ETA, I'd be interested :)

Thanks,
Simon

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675114

Title:
  QEMU seccomp sandbox missing a whitelist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1675114/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to