3 ms·
Title is misleading since that bug only happens on some systems and will not introduce any remote execution. This bug also has a Priority of 'high' and not 'cri
by merb 11y ago
Title is misleading since that bug only happens on some systems and will not introduce any remote execution.
This bug also has a Priority of 'high' and not 'critical', since you could actually just go back to the latest kernel.
Edit: I have 10 systems on this kernel and all of them are working.
- nailer 11y agoIt also seems, from a few minutes research, that the fix is available with an OS point release update, the only thing being held back is the z-stream (fix without point release update). Disclaimer: worked at Red Hat more than a decade ago.
- flyinghamster 11y agoThat could be six months or a year from now. I don't like the idea of having to put "exclude=kernel*" in my yum.conf.
- flyinghamster 11y agoChanged title, but still, I'd call "crashes on boot" a critical bug. Interest: I have an affected system, and discovered the crash when I upgraded to CentOS 7-1511. Until this gets fixed, I'm stuck on the last working kernel, though I could use the mainline kernel from ELRepo. Otherwise, it's "hello, Ubuntu Server."