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.
Bug 1679468 - avc: denied { signull } for comm="systemd-journal"
Summary: avc: denied { signull } for comm="systemd-journal"
Keywords:
Status: CLOSED DUPLICATE of bug 1676923
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: selinux-policy
Version: 8.0
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-21 08:08 UTC by Martin Pitt
Modified: 2019-05-22 04:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-21 09:08:35 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Martin Pitt 2019-02-21 08:08:09 UTC 
Description of problem:

A *very* recent update in RHEL 8.0 nightlies now causes the following SELinux violation variations at every boot:

avc:  denied  { signull } for  pid=580 comm="systemd-journal" scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:system_r:crond_t:s0-s0:c0.c1023 tclass=process permissive=0
avc:  denied  { signull } for  pid=580 comm="systemd-journal" scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:system_r:NetworkManager_t:s0 tclass=process permissive=0
avc:  denied  { signull } for  pid=580 comm="systemd-journal" scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:system_r:sshd_t:s0-s0:c0.c1023 tclass=process permissive=0
avc:  denied  { signull } for  pid=580 comm="systemd-journal" scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:system_r:sssd_t:s0 tclass=process permissive=0
avc:  denied  { signull } for  pid=580 comm="systemd-journal" scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:system_r:systemd_logind_t:s0 tclass=process permissive=0
avc:  denied  { signull } for  pid=580 comm="systemd-journal" scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:system_r:systemd_machined_t:s0 tclass=process permissive=0
avc:  denied  { signull } for  pid=580 comm="systemd-journal" scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:system_r:udev_t:s0-s0:c0.c1023 tclass=process permissive=0


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

selinux-policy-targeted-3.14.1-60.el8.noarch
systemd-239-4.el8.x86_64
kernel 4.18.0-69.el8                                    

How reproducible: Always

Steps to Reproduce:
1. Boot current nightly

Additional info: Our previously built image from February 14 did not have that problem. Same systemd version, but selinux-policy version was 3.14.1-59.el8.noarch, and kernel at 4.18.0-67. So the regression is likely between the two latter.
Comment 1 Lukas Vrabec 2019-02-21 09:08:35 UTC 

*** This bug has been marked as a duplicate of bug 1676923 ***
Note You need to log in before you can comment on or make changes to this bug.