Control: tags -1 + unreproducible fixed-upstream Control: forwarded -1 https://repo.or.cz/iotop.git/commit/7c51ce0e29bd135c216f18e18f0c4ab769af0d6f https://repo.or.cz/iotop.git/commit/0392b205b5c3973a326721c2e9f97f0fa2eefa82
On Mon, 2019-04-01 at 16:43 -0600, Neil Tallim wrote: > I'm afraid there's a flaw in the version of iotop available in Debian (even in > sid): retpoline support adds a blank line to /proc/<pid>/status, which iotop > was > not able to deal with before May of 2018. The effect of this is a crash with a > Python stack-trace. It affects all usage of iotop on any kernels with spectre > mitigation. As far as I can tell the commit that added blank lines to the /proc/*/status files was never added to Debian or mainline kernels and indeed iotop works for me with Linux 4.19.28-2 from Debian unstable. Could you provide some info I can use to reproduce this? $ uname -rv 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) $ sudo sh -c 'grep -l "^ *$" /proc/*/status' $ cat /sys/devices/system/cpu/vulnerabilities/spectre_v2 Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
