Comment 11 for bug 1715519

Revision history for this message
Daniel Axtens (daxtens) wrote :

Hi,

As well as Po-Hsu's comment above, I also have this internal update from the kernel team:

    As this is also a security fix, don't stress too much. If things could be verified for at least for one of the kernels until next week that is better than nothing. We are rather unlikely rip out fixes if they have a CVE (and do not appear to regress other things)

(FYI, this issue is covered by CVE-2018-1000026.)

So, just to confirm, in order of priority:

 1) First confirm there are no new regressions (just a quick 'smoke test') on the 3 kernels.

 2) Second, do a full test of 1 of the kernels.

 3) Test the remaining 2 kernels.

Please keep this bug updated as you go through each step.

Hopefully this helps reduce the pressure for you!

Regards,
Daniel