** Changed in: iotop (Ubuntu Xenial)
Status: Confirmed => Invalid
** Changed in: iotop (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Tyler Hicks (tyhicks)
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Description changed:
+ [Impact]
+ The CVE-2018-3639 for Xenial introduced a double newline sequence in the
/proc/PID/status files. This breaks some userspace tools, such as iotop, that
parse those files.
+
+ [Test Case]
+ Incorrect output in 4.4.0-127.153-generic:
+
+ $ cat /proc/self/status
+ ...
+ Seccomp: 0
+
+ Speculation_Store_Bypass: thread vulnerable
+ ...
+
+ Expected output:
+
+ $ cat /proc/self/status
+ ...
+ Seccomp: 0
+ Speculation_Store_Bypass: thread vulnerable
+ ...
+
+ [Regression Potential]
+ None
+
+ [Original Report]
+
Hello,
after running updates today to linux-
image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop
is not working any more. Reason are empty lines in /proc/PID/status,
which confuse iotop (and me)
In new view there is an empy line between Seccomp and
Speculation_Store_Bypass:
####
Seccomp: 0
Speculation_Store_Bypass: vulnerable
####
Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a
relation to spectre/meltdown patches.
iotop is first application which is failing here, but iam afraid of
more.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772671
Title:
Kernel produces empty lines in /proc/PID/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iotop/+bug/1772671/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
