The 201 build fixes a possible data corruption bug in the previous 4.0.4 build. The 4.0.4 stable kernel update contains a number of important fixes across the tree. The 4.0.3 rebase contains improved hardware support, a number of new features, and many important fixes across the tree. The 3.19.8 update contains an number of important fixes across the tree.
sudo dnf upgrade --refresh --advisory=FEDORA-2015-8737Please login to add feedback.
| 0 | 0 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
Taskotron: depcheck test PASSED on i386. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/72428/steps/runtask/logs/stdio (results are informative only)
Taskotron: depcheck test PASSED on x86_64. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/72428/steps/runtask/logs/stdio (results are informative only)
Bug 1223332 is fixed. Lots of IO completed without corruption.
This update is currently being pushed to the Fedora 21 testing updates repository.
No regressions noted in everyday use on my E531. (The same was true of 4.0.3 and the earlier 4.0.4 build for me, since I don't use RAID0.)
Critical path update approved
This update has been pushed to testing
Bug 1223332 did not apply to me, but this kernel is operating without issue on several of my x86_64 server & desktop machines.
works for me
This update has been submitted for stable by jforbes.
Taskotron: upgradepath test PASSED on noarch. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/72941/steps/runtask/logs/stdio (results are informative only)
This update is currently being pushed to the Fedora 21 stable updates repository.
This update has been pushed to stable
I hope I'm not too late, but this contains an unpleasant regression that breaks some namespace users. The fix is already in Fedora git: http://pkgs.fedoraproject.org/cgit/kernel.git/commit/?h=f22&id=d7c3b932a43f90a0a5bf086f4795120044ab1460 It might be nice to either unpush this or to push a newer version ASAP.
To be clear, due to the bug amluto references, an unprivileged user can cause this kernel to panic, and anyone running Sandstorm.io or various other containerization stuff will see panics.
This update has already been pushed to stable, karma has no impact by this time. Interestingly, 4.0.x updates have spent over 10 days in updates-testing and this is the first time someone thought to bodhi comment on it. The fix is already in Fedora git for all impacted kernels and will be included in the next builds
We reported the problem to pjp of Fedora security a week ago.
We've not heard from the Fedora security team regarding this issue. I was notified about it from Alex Larsson yesterday.
Okay, said issue is fixed in the 4.0.4-202 update filed today