Bug 1692843

Summary: ps reports numerical CLS value of "#6" for SCHED_DEADLINE policy tasks instead of DLN
Product: Red Hat Enterprise Linux 7 Reporter: nyelle <nyelle>
Component: procps-ngAssignee: Jan Rybar <jrybar>
Status: CLOSED ERRATA QA Contact: Karel Volný <kvolny>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.6CC: kvolny
Target Milestone: rcKeywords: EasyFix, Patch, Upstream
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: procps-ng-3.3.10-25.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 13:03:38 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:

Description nyelle@redhat.com 2019-03-26 14:35:35 UTC 
Description of problem:
RHEL 7.6 kernel introduces a new scheduling policy SCHED_DEADLINE.
ps does not convert this policy value to a human readable string and instead prints "#6" for CLS value.


Version-Release number of selected component (if applicable):'
kernel-3.10.0-957.el7.x86_64
procps-ng-3.3.10-23.el7.x86_64

How reproducible:
Every time


Steps to Reproduce:
1. Assign deadline policy to some task

# chrt -d --sched-runtime 1000000 --sched-deadline 5000000 --sched-period 5000000 0 sleep 100&
[1] 20814


2. Check the task in ps:

# ps -efac
UID        PID  PPID CLS PRI STIME TTY          TIME CMD
root     20814 19603 #6  140 10:31 pts/0    00:00:00 sleep 100


Actual results:
UID        PID  PPID CLS PRI STIME TTY          TIME CMD
root     20814 19603 #6  140 10:31 pts/0    00:00:00 sleep 100

Expected results:

In RHEL 8 this works:
UID        PID  PPID CLS PRI STIME TTY          TIME CMD
root     20848 20487 DLN 140 10:00 pts/0    00:00:00 sleep 100000

Additional info:

ps: recognize SCHED_DEADLINE
https://gitlab.com/procps-ng/procps/commit/f8ccf3126e160987141d9991fa9524eda6265ed6
Comment 7 errata-xmlrpc 2019-08-06 13:03:38 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, 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/RHSA-2019:2189