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.

Description of problem:

On one ARM machine, we've observed /dev/tmc_etr0 and /dev/tmc_etr1 with device_t type.

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

selinux-policy-34.1.18-1.el9.noarch

How reproducible:

Deterministic.

Steps to Reproduce:
1. ls -laZ /dev/tmc_etr* | grep device_t

Actual results:

crw-------. 1 root root system_u:object_r:device_t:s0 10, 124 Dec  6  2021 /dev/tmc_etr0
crw-------. 1 root root system_u:object_r:device_t:s0 10, 122 Dec  6  2021 /dev/tmc_etr1

Expected results:

No output.

Additional info:

Ondrej,

Can you help me with understanding these devices purpose? Do we need a new type? I've found them in drivers/hwtracing/coresight:

tmc_etb
tmc_etf
tmc_etr
possibly also
etb
stm
tpiu

The request was for /dev/tmc_etr[0-9]+ only though.

The devices seem to be intended for HW-level tracing and debugging of software (I guess mainly for low-level performance debugging) [1]. I can't see any suitable existing type in the policy - perhaps a new hwtracing_device_t would be best? (We could then reuse it for other devices coming from drivers/hwtracing if needed.)

[1] https://developer.arm.com/ip-products/system-ip/coresight-debug-and-trace

I've submitted a Fedora PR to address the issue:
https://github.com/fedora-selinux/selinux-policy/pull/975

Please note only a new type was added for the devices, no actual access allowed for domains which do not have access to the device_node attribute.

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 (new packages: selinux-policy), 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:3918