Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
type=AVC msg=audit(1455729417.967:1376): avc: denied { write } for pid=12653 comm="systemd-notify" name="kmsg" dev="devtmpfs" ino=1034 scontext=system_u:system_r:systemd_notify_t:s0 tcontext=system_u:object_r:kmsg_device_t:s0 tclass=chr_file type=SYSCALL msg=audit(1455729417.967:1376): arch=c000003e syscall=2 success=no exit=-13 a0=7f3b0224dcd4 a1=80101 a2=ffffffff a3=7f3b019e37b8 items=0 ppid=1 pid=12653 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-notify" exe="/usr/bin/systemd-notify" subj=system_u:system_r:systemd_notify_t:s0 key=(null)
type=AVC msg=audit(1455731077.537:1411): avc: denied { open } for pid=12608 comm="systemd-notify" path="/dev/kmsg" dev="devtmpfs" ino=1034 scontext=system_u:system_r:systemd_notify_t:s0 tcontext=system_u:object_r:kmsg_device_t:s0 tclass=chr_file type=SYSCALL msg=audit(1455731077.537:1411): arch=c000003e syscall=2 success=no exit=-13 a0=7f7e9a7b8cd4 a1=80101 a2=ffffffff a3=7f7e99f4e7b8 items=0 ppid=1 pid=12608 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-notify" exe="/usr/bin/systemd-notify" subj=system_u:system_r:systemd_notify_t:s0 key=(null)
Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.13.1-60.el7_2.3.noarch
systemd-219-19.el7_2.4.x86_64
How reproducible:
Everytime, see above and below.
Actual results:
AVC denied messages related to kmsg_device_t since latest updates.
Expected results:
No AVC denied messages related to kmsg_device_t.
Additional info:
No matter if it's related or not, but during boot we see the following about
a zillion times on the screen:
systemd-journald[...]: /dev/kmsg buffer overrun, some messages lost
Btw, note that above messages are from two different reboots, we just allowed
the first before the second reboot when rebooting with permissive, however we
did not see more messages in permissive. Unfortunately we were also not able
to track down the origin and if there's a relation to the overrun messages.
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, 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://rhn.redhat.com/errata/RHBA-2016-2283.html
Description of problem: type=AVC msg=audit(1455729417.967:1376): avc: denied { write } for pid=12653 comm="systemd-notify" name="kmsg" dev="devtmpfs" ino=1034 scontext=system_u:system_r:systemd_notify_t:s0 tcontext=system_u:object_r:kmsg_device_t:s0 tclass=chr_file type=SYSCALL msg=audit(1455729417.967:1376): arch=c000003e syscall=2 success=no exit=-13 a0=7f3b0224dcd4 a1=80101 a2=ffffffff a3=7f3b019e37b8 items=0 ppid=1 pid=12653 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-notify" exe="/usr/bin/systemd-notify" subj=system_u:system_r:systemd_notify_t:s0 key=(null) type=AVC msg=audit(1455731077.537:1411): avc: denied { open } for pid=12608 comm="systemd-notify" path="/dev/kmsg" dev="devtmpfs" ino=1034 scontext=system_u:system_r:systemd_notify_t:s0 tcontext=system_u:object_r:kmsg_device_t:s0 tclass=chr_file type=SYSCALL msg=audit(1455731077.537:1411): arch=c000003e syscall=2 success=no exit=-13 a0=7f7e9a7b8cd4 a1=80101 a2=ffffffff a3=7f7e99f4e7b8 items=0 ppid=1 pid=12608 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-notify" exe="/usr/bin/systemd-notify" subj=system_u:system_r:systemd_notify_t:s0 key=(null) Version-Release number of selected component (if applicable): selinux-policy-targeted-3.13.1-60.el7_2.3.noarch systemd-219-19.el7_2.4.x86_64 How reproducible: Everytime, see above and below. Actual results: AVC denied messages related to kmsg_device_t since latest updates. Expected results: No AVC denied messages related to kmsg_device_t. Additional info: No matter if it's related or not, but during boot we see the following about a zillion times on the screen: systemd-journald[...]: /dev/kmsg buffer overrun, some messages lost