-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-9.6
-
None
-
No
-
Moderate
-
rhel-sst-security-selinux
-
ssg_security
-
None
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
None
-
None
-
x86_64
-
None
Logging this ticket against RHEL 9 - however the issue has been reproduced on Fedora 40.
In Fedora 40 with any kernel version it has been noticed that most of the debugfs entries for the QAT driver are not present after starting the qat service.
The debugfs folder reports only the key dev_cfg which is created at the startup of the driver.
This is caused by SELinux blocking the creation of debugfs entries in the driver. If SELinux is in permissive mode or disabled, this issue does not occur.
Attached the output of /var/log/audit/audit.log when this issue occurs with SELinux in permissive mode.
What were you trying to do that didn't work?
Installing and using QATlib
Please provide the package NVR for which bug is seen:
qatlib
How reproducible:
100% on Fedora 40
Steps to reproduce
- Make sure that the qat driver is loaded - you need a platform with Intel QAT and 4xxx (SPR, EMR or SRF)
- Check that the debugfs entries are present in /sys/kernel/debug/qat*/...
- Install qatlib
- Start the qat service
- Check the debugfs entries for the qat driver in /sys/kernel/debug/qat*/...
Expected results
Example:
root@fedora:/sys/kernel/debug/qat_4xxx_0000:e8:00.0# ls cnv_errors dev_cfg fw_counters heartbeat pm_status telemetry transport
Actual results
root@fedora:/sys/kernel/debug/qat_4xxx_0000:e8:00.0# ls dev_cfg
- is cloned by
-
RHEL-66334 [RHEL-10] QAT debugfs entries not present after restarting qat service in QATlib
- Planning