Bug 2040249

Summary: device_t findings based on mass-modprobe
Product: Red Hat Enterprise Linux 9 Reporter: Jiri Jaburek <jjaburek>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED WONTFIX QA Contact: Milos Malik <mmalik>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.0CC: lvrabec, mmalik, nknazeko
Target Milestone: rcKeywords: Triaged
Target Release: 9.3   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-13 07:31:54 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 Jiri Jaburek 2022-01-13 10:08:41 UTC 
Description of problem:

(I asked mmalik and he mentioned it would be easier to file these in one BZ instead of separately, so here you go.)

After doing (the equivalent of):

find /lib/modules/`uname -r`/kernel -type f | sed 's/\.ko\.xz//' | xargs -n1 basename | sort -u | xargs -n1 modprobe

these devices are created and have device_t:

# all architectures (?)
/dev/aer_inject
/dev/ubi_ctrl
/dev/nullb0

# ppc64le LPAR
/dev/ibmvmc

# s390x kvm
/dev/chsc

# s390x z/VM
/dev/symptom
/dev/account
/dev/logrec

# x86_64 (both UEFI and non-UEFI)
/dev/dummy_stm.3
/dev/dummy_stm.2
/dev/dummy_stm.1
/dev/dummy_stm.0
/dev/qat_adf_ctl
/dev/erst_dbg


Version-Release number of selected component (if applicable):
RHEL-9.0.0-20220111.1
selinux-policy-34.1.20-1.el9.noarch
Comment 9 RHEL Program Management 2023-07-13 07:31:54 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.