Source: iotop
Version: 0.6-42-ga14256a-0.3
Severity: normal
Tags: upstream patch
X-Debbugs-Cc: br...@canonical.com

Running `iotop-py -o` should suppress display of processes with no IO.
This behaves correctly on older kernels but with 6.14 it does not.

[Steps to Reproduce]
$ lxc launch ubuntu-daily:24.10/amd64 iotop-fix-lp2111673-oracular --vm 
--config limits.memory=16GB --device root,size=50GB --profile standard
$ lxc exec iotop-fix-lp2111673-oracular -- bash
# apt-get -y install iotop
# apt-cache policy iotop | grep Installed:
  Installed: 0.6-42-ga14256a-0.2build1
# which iotop-py
/usr/sbin/iotop-py
# uname -a
Linux iotop-fix-lp2111673-oracular 6.11.0-26-generic #26-Ubuntu SMP 
PREEMPT_DYNAMIC Sat Apr 12 11:25:41 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
# iotop-py -o
Total DISK READ: 0.00 B/s | Total DISK WRITE: 0.00 B/s
Current DISK READ: 0.00 B/s | Current DISK WRITE: 0.00 B/s
    TID PRIO USER DISK READ DISK WRITE> COMMAND

---

$ lxc launch ubuntu-daily:25.04/amd64 iotop-fix-lp2111673-plucky --vm --config 
limits.memory=16GB --device root,size=50GB --profile standard
$ lxc exec iotop-fix-lp2111673-plucky -- bash
# apt-get -y install iotop
# apt-cache policy iotop | grep Installed:
  Installed: 0.6-42-ga14256a-0.3build1
# which iotop-py
/usr/sbin/iotop-py
# uname -a
Linux iotop-fix-lp2111673-plucky 6.14.0-15-generic #15-Ubuntu SMP 
PREEMPT_DYNAMIC Sun Apr 6 15:05:05 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
# iotop-py -o
Total DISK READ: 0.00 B/s | Total DISK WRITE: 0.00 B/s
Current DISK READ: 0.00 B/s | Current DISK WRITE: 0.00 B/s
    TID PRIO USER DISK READ DISK WRITE> COMMAND
   1596 be/4 root 0.00 B/s 0.00 B/s python3 /usr/sbin/iotop-py -o


As can be seen in that final line, the iotop-py process (which is
running in both examples) is suppressed in the original case
but is incorrectly included for display in the second.


[Potential Fix]

I found some changes in the upstream project that seem relevant,
although I have not tested them:

https://github.com/Tomas-M/iotop/compare/dec34cdebd7935ef82c24258eead595496d45cbf~1..b716e7ea16c16444f11ef8a8270f1678d08d586b

Also followon fixes:

886ec669368a86ea9fc176cda8897ef7954942a2
6e96ccba9586c372a87cb1d6a06d1fa9a9fc5375
eb3791185f12fadc19102c6ddc0c29ecfd41fccb
504317f644cbf24165008567d6c2cf498d6408e4


[Ubuntu Bug]

This is an issue originally reported against Ubuntu, here:

  https://bugs.launchpad.net/ubuntu/+source/iotop/+bug/2111673

Bryce

Reply via email to