5 ms·
That range isn't quite correct. It only impacted 4.13 kernels, and only 4.13.0-4.13.6 (inclusive, distro-dependent due to backports). It was patched in 4.13.7
by TheDong 9y ago
That range isn't quite correct. It only impacted 4.13 kernels, and only 4.13.0-4.13.6 (inclusive, distro-dependent due to backports).
It was patched in 4.13.7 after being introduced in the 4.13.0 merge window.
See https://lwn.net/Articles/736348/ https://lwn.net/Articles/736348/
This issue shouldn't have happened at all, but it was caught and patched very quickly, so relatively few real-world systems are or were affected.
- cirowrc 9y agoThanks!
- Da5hes 9y agoit was introduced by this commmit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4c48abe91be03d191d0c20cc755877da2cb35622 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin... which by itself is in a 4.12 vanilla code tree
- TheDong 9y agoThat commit is correct (4c48abe91be03d191d0c20cc755877da2cb35622), but it was not in 4.12 as cut by linus. https://github.com/torvalds/linux/commit/4c48abe91be03d191d0c20cc755877da2cb35622 https://github.com/torvalds/linux/commit/4c48abe91be03d191d0... (click the little '...' to expand tags it's in) or: $ git tag --contains 4c48abe91be03d191d0c20cc755877da2cb35622 v4.13 What is your methodology that gets that it is in the 4.12 tree?
- Da5hes 9y agoyou are right, i actually didn't check on git, my bad