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:


While running regression tests for GFS2 we are seeing AVC denials:

time->Fri Jun 10 04:20:23 2022
type=PROCTITLE msg=audit(1654827623.043:2125): proctitle=646C6D5F636F6E74726F6C64002D730030
type=SYSCALL msg=audit(1654827623.043:2125): arch=c000003e syscall=62 success=no exit=-13 a0=d746 a1=0 a2=1 a3=7ffe104ebfc0 items=0 ppid=1 pid=55328 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dlm_controld" exe="/usr/sbin/dlm_controld" subj=system_u:system_r:dlm_controld_t:s0 key=(null)
type=AVC msg=audit(1654827623.043:2125): avc:  denied  { signull } for  pid=55328 comm="dlm_controld" scontext=system_u:system_r:dlm_controld_t:s0 tcontext=system_u:system_r:cluster_t:s0 tclass=process permissive=0

The following needs to be added to the SELinux policy

#============= dlm_controld_t ==============
allow dlm_controld_t cluster_t:process signull;

Version-Release number of selected component (if applicable):
selinux-policy-34.1.33-1.el9

How reproducible:
Easily

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Nate,

Could you switch the system to SELinux permissive mode to gather subsequent denials, or try this workaround to see if it is sufficient?

  # cat local_dlm_cluster_sig.cil
(allow dlm_controld_t cluster_t (process (signull)))

  # semodule -i local_dlm_cluster_sig.cil

I ran the tests again with SELinux permissive mode and no other AVC's came out.

Commit to backport:
commit 4b05c9c89c39d820f8fe8f72da02f5df5fbc79d2
Author: Zdenek Pytela <zpytela>
Date:   Fri Jun 17 23:45:16 2022 +0200

    Allow dlm_controld send a null signal to a cluster daemon

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 (selinux-policy bug fix and enhancement update), 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:8283