Bug 2223218

Summary: SELinux is preventing systemd-journal from 'write' accesses on the file memory.pressure.
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 38CC: dwalsh, ian.laurie, lvrabec, mikhail.v.gavrilov, mmalik, nknazeko, omosnacek, pkoncity, vmojzis, zpytela
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:897ace4c38ed55b9971900722b7a344a092bb2475172dc5b65f60e67c375a51f;VARIANT_ID=workstation;
Fixed In Version: selinux-policy-38.24-1.fc38 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-12 04:22:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: description
none
File: os_info none

Description Mikhail 2023-07-16 20:02:23 UTC
Description of problem:
SELinux is preventing systemd-journal from 'write' accesses on the file memory.pressure.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that systemd-journal should be allowed write access on the memory.pressure file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'systemd-journal' --raw | audit2allow -M my-systemdjournal
# semodule -X 300 -i my-systemdjournal.pp

Additional Information:
Source Context                system_u:system_r:syslogd_t:s0
Target Context                system_u:object_r:cgroup_t:s0
Target Objects                memory.pressure [ file ]
Source                        systemd-journal
Source Path                   systemd-journal
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-38.20-1.fc39.noarch
Local Policy RPM              selinux-policy-targeted-38.20-1.fc39.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed) 6.5.0-
                              0.rc1.20230711git3f01e9fed845.13.fc39.x86_64+debug
                              #1 SMP PREEMPT_DYNAMIC Sat Jul 15 00:20:03 +05
                              2023 x86_64
Alert Count                   1
First Seen                    2023-07-16 21:06:16 +05
Last Seen                     2023-07-16 21:06:16 +05
Local ID                      d74d4123-f3f6-4d6b-b24e-7f92a6ea29c2

Raw Audit Messages
type=AVC msg=audit(1689523576.927:1727): avc:  denied  { write } for  pid=56827 comm="systemd-journal" name="memory.pressure" dev="cgroup2" ino=20421 scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:object_r:cgroup_t:s0 tclass=file permissive=1


Hash: systemd-journal,syslogd_t,cgroup_t,file,write

Version-Release number of selected component:
selinux-policy-targeted-38.20-1.fc39.noarch

Additional info:
reporter:       libreport-2.17.11
reason:         SELinux is preventing systemd-journal from 'write' accesses on the file memory.pressure.
package:        selinux-policy-targeted-38.20-1.fc39.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.5.0-0.rc1.20230711git3f01e9fed845.13.fc39.x86_64+debug
component:      selinux-policy

Comment 1 Mikhail 2023-07-16 20:02:25 UTC
Created attachment 1976081 [details]
File: description

Comment 2 Mikhail 2023-07-16 20:02:27 UTC
Created attachment 1976082 [details]
File: os_info

Comment 3 Zdenek Pytela 2023-07-18 19:15:35 UTC
*** Bug 2223758 has been marked as a duplicate of this bug. ***

Comment 4 Zdenek Pytela 2023-07-21 12:32:51 UTC
*** Bug 2224460 has been marked as a duplicate of this bug. ***

Comment 5 Zdenek Pytela 2023-07-31 08:02:19 UTC
*** Bug 2227455 has been marked as a duplicate of this bug. ***

Comment 6 Fedora Update System 2023-08-07 07:04:26 UTC
FEDORA-2023-a79a6bdd37 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a79a6bdd37

Comment 7 Fedora Update System 2023-08-08 01:56:35 UTC
FEDORA-2023-a79a6bdd37 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-a79a6bdd37`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a79a6bdd37

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2023-08-12 04:22:46 UTC
FEDORA-2023-a79a6bdd37 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.