Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1679201

Summary: The 'iotop -p' command reports that 'CONFIG_TASK_DELAY_ACCT not enabled in kernel' if an invalid <PID> or kernel thread <PID> is used.
Product: Red Hat Enterprise Linux 8 Reporter: Abhijeet Joshi <abjoshi>
Component: iotopAssignee: Michal Hlavinka <mhlavink>
Status: CLOSED ERRATA QA Contact: Evgeny Fedin <efedin>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: abjoshi, dev, efedin, jan.public, kb, nyewale
Target Milestone: rcKeywords: Patch, Triaged
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: iotop-0.6-17.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2052422 (view as bug list) Environment:
Last Closed: 2022-05-10 15:32:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2052422    

Description Abhijeet Joshi 2019-02-20 15:17:11 UTC
Description of problem:
* The command 'iotop -p' reports that 'CONFIG_TASK_DELAY_ACCT not enabled in kernel' if an invalid <PID> or kernel thread is used.

* [root@rhel8testing ~]# egrep 'CONFIG_TASK_DELAY_ACCT|CONFIG_TASK_IO_ACCOUNTING|CONFIG_TASKSTATS|CONFIG_VM_EVENT_COUNTERS' /boot/config-4.18.0-32.el8.x86_64 
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_VM_EVENT_COUNTERS=y


Version-Release number of selected component (if applicable):

* [root@rhel8testing ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.0 Beta (Ootpa)

* [root@rhel8testing ~]# rpm -qa | grep iotop
iotop-0.6-16.el8.noarch

How reproducible:
* Always reproducible. 


Steps to Reproduce:

[1] Install iotop package.
--------------------
# yum install iotop
--------------------


[2] Execute the 'iotop -p' command with an invalid PID of kernel thread PID.

Eg:
# [root@rhel8testing ~]# ps aufx | grep 20000
root     23306  0.0  0.1 219332   912 pts/1    S+   20:28   0:00              \_ grep --color=auto 20000


# iotop -p 20000
------------------------------------------------------------
Below is the output after executing the above command:

Total DISK READ :	0.00 B/s | Total DISK WRITE :       0.00 B/s
Actual DISK READ:	0.00 B/s | Actual DISK WRITE:       0.00 B/s
  TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND                                                                            


CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO %
------------------------------------------------------------


* Similarly refer to the below output as well:

# iotop -p 3

------------------------------------------------------------------------
Total DISK READ :	0.00 B/s | Total DISK WRITE :       0.00 B/s
Actual DISK READ:	0.00 B/s | Actual DISK WRITE:       0.00 B/s
  TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND                                                                            
    3 be/0 root        0.00 B/s    0.00 B/s  ?unavailable?  [rcu_gp]

CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO %
------------------------------------------------------------------------


Actual results:

* The iotop reports the below message that the kernel configuration item CONFIG_TASK_DELAY_ACCT is not enabled.
-------------------------------------
CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO %
-------------------------------------

Expected results:

* The misleading message about kernel configuration item CONFIG_TASK_DELAY_ACCT should not appear.

Comment 2 Kai Bojens 2021-10-15 18:26:40 UTC
I can confirm this for Fedora 34 and Kernel 5.14.11-200.fc34.x86_64 with "iotop -oa":

CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO %

Comment 3 Sidney Sedlak 2021-10-31 16:45:43 UTC
Same for me on Fedora 34, see this thread: https://www.spinics.net/lists/kernel/msg4052926.html

As a workaround, boot with 'delayacct' argument.

Comment 4 Michal Hlavinka 2022-01-12 10:58:07 UTC
*** Bug 2035897 has been marked as a duplicate of this bug. ***

Comment 5 Michal Hlavinka 2022-01-12 11:04:33 UTC
reproducible

Comment 6 Michal Hlavinka 2022-02-09 09:04:23 UTC
fixed in fedora iotop-0.6-31.fc37

Comment 13 errata-xmlrpc 2022-05-10 15:32:51 UTC
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 (iotop bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2022:2116