Bug 2040249 - device_t findings based on mass-modprobe
Summary: device_t findings based on mass-modprobe
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: selinux-policy
Version: 9.0
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: 9.3
Assignee: Zdenek Pytela
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-13 10:08 UTC by Jiri Jaburek
Modified: 2023-07-13 07:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-13 07:31:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-107799 0 None None None 2022-01-13 10:11:58 UTC

Internal Links: 2039774

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.


Note You need to log in before you can comment on or make changes to this bug.