Red Hat Bugzilla – Bug 1245677
The current regex solution breaks tuna and possible others apps with newer kernels
Last modified: 2016-11-04 04:08:00 EDT
Description of problem: The /proc/interrupts format changed a bit in the newer kernels adding an extra column. This is how it used to be: 43: 0 0 0 0 PCI-MSI-edge virtio0-input.0 This is how it is now: 43: 0 0 0 0 PCI-MSI 32769-edge virtio0-input.0 The extra column breaks the 'users' parser. As a consequence tuna breaks too. # tuna --irqs='virtio0*' --cpus=0,1,2,3 -x [] tuna: --move requires a list of threads/irqs! [root@localhost ~]# tuna --irqs='*virtio0*' --cpus=0,1,2,3 -x [32, 33, 34, 26, 27, 28, 29, 30, 31] Version-Release number of selected component (if applicable): tuna-0.11.1-8.el7.noarch python-linux-procfs-0.4.6-2.el7.noarch Good kernel: 3.10.0-252.el7.x86_64 Bad kernel: vmlinuz-4.1.0-05824-gb922622 How reproducible: Always, just reboot a guest using the bad kernel version. Actual results: tuna regex for irq users is broken Expected results: both kernels are supported and the same regex applies. Additional info: The bad kernel might not be supported at this moment, but it is useful for testing and might be the case of more advanced kernels, like kernel-rt. In any case, this needs to be fixed to prevent customers to find it later on when the supported kernel gets updated too.
Fixed upstream: https://git.kernel.org/cgit/libs/python/python-linux-procfs/python-linux-procfs.git/commit/?id=c7f561f5acbabb095c22709a1878e484e1134ae2
The patch to fix this was included in bz1235826
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2532.html