Now this is mostly for squashing the recently announced critical:
x86, x32: Correct invalid use of user timespec in the kernel (CVE-2014-0038)
I will write a better advisory tomorrow, but so you can start testing:
Steps to Reproduce:
When testing these alternative kernels (-linus, -rt, -tmb, -vserver) it is necessary to use the dkms driver packages, dkms-nvidia* and dkms-fglrx etc. rather than the pre-built kmod packages such as nvidia-current-kernel-desktop-latest.
Pre-built kmod packages only support the specific kernel they are built for, which forms part of the package name.
Dkms packages actually build the driver on the next boot for whichever kernel you are using. It means the first boot after installing the new kernel will take longer than expected. Allow it to complete, normally a minute or couple of minutes, depending on your hardware. You can see it building if you remove "splash quiet" options from the kernel command line or press escape as it boots so you can see the text. It shows and a series of dots ". . . . ."
This kernel update provides an update to 3.12.9 and fixes the following
critical security issue:
Pageexec reported a bug in the Linux kernel's recvmmsg syscall when called
from code using the x32 ABI. An unprivileged local user could exploit this
flaw to cause a denial of service (system crash) or gain administrator
For other changes, see the referenced changelog:
No splash screen during boot, but dkms packages build normally. The first video shown is, in my case, the nvidia splash screen. I asked tmb about it on irc and he would rather not delay the security update with a rebuild.
tmb wrw105, yeah, they are "OK" as such as it's not a regression from x86_64 release kernels... seems I never enabled FB_SIMPLE on them even if I did for i586
tmb I'll queue it up for next update but I'd rather not delay the security fix
otherwise these are OK for me. I'll give it a couple of hours and if nobody else chimes in I'll OK mga4-64.
Splash screen is present, apparently dkms modules build at install.
Boot into system is normal.
If no other testers in the next few hours, I'll ok both 32 and 64 bit for advisory upload to svn and validation.
Testing complete mga4 x86_64,Nothing to report, all seems work nice on my laptop.
Testing complete mga4 i586, Nothing to report, all seems work nice on my laptop.
Advisory uploaded. Validating.
Could sysadmin please push to 4 updates
MGA4-64-OK MGA4-32-OK =>
advisory MGA4-64-OK MGA4-32-OKCC: