Bug 2312417
| Summary: | SELinux denial on every reboot | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | George Petasis <petasisg> |
| Component: | mysql-selinux | Assignee: | Michal Schorm <mschorm> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 40 | CC: | adobes, hhorak, ljavorsk, mbayer, mmuzila, mschorm, SpikeFedora, zmiklank |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | mysql-selinux-1.0.11-1.fc41 mysql-selinux-1.0.11-1.fc39 mysql-selinux-1.0.11-1.fc40 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-09-25 01:29:17 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: | |||
FEDORA-2024-3721532bce (mysql-selinux-1.0.11-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-3721532bce FEDORA-2024-28bb0038ce (mysql-selinux-1.0.11-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-28bb0038ce FEDORA-2024-4f35baf4d4 (mysql-selinux-1.0.11-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-4f35baf4d4 FEDORA-2024-4f35baf4d4 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-4f35baf4d4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-4f35baf4d4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-28bb0038ce has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-28bb0038ce` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-28bb0038ce See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-3721532bce has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-3721532bce` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-3721532bce See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-4f35baf4d4 (mysql-selinux-1.0.11-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-28bb0038ce (mysql-selinux-1.0.11-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-3721532bce (mysql-selinux-1.0.11-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. |
1. Please describe the problem: I am getting this SELinux denial on every boot: SELinux is preventing mariadbd from write access on the file memory.pressure. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that mariadbd 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 'mariadbd' --raw | audit2allow -M my-mariadbd # semodule -X 300 -i my-mariadbd.pp Additional Information: Source Context system_u:system_r:mysqld_t:s0 Target Context system_u:object_r:cgroup_t:s0 Target Objects memory.pressure [ file ] Source mariadbd Source Path mariadbd ???? <???????> Host fedser-aero Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-40.27-1.fc40.noarch Local Policy RPM mysql-selinux-1.0.10-3.fc40.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name fedser-aero Platform Linux fedser-aero 6.10.9-200.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Sep 8 17:23:55 UTC 2024 x86_64 Alert Count 29 First Seen 2024-09-12 19:52:27 EEST Last Seen 2024-09-15 10:42:33 EEST Local ID 8cdcea09-cadb-49dd-8048-f54800e9bcb5 Raw Audit Messages type=AVC msg=audit(1726386153.412:236): avc: denied { write } for pid=5613 comm="mariadbd" name="memory.pressure" dev="cgroup2" ino=6452 scontext=system_u:system_r:mysqld_t:s0 tcontext=system_u:object_r:cgroup_t:s0 tclass=file permissive=0 Hash: mariadbd,mysqld_t,cgroup_t,file,write 2. Specify used package versions # dnf list installed | grep -i -e maria -e mysql -e galera mariadb.x86_64 3:10.11.8-3.fc40 @updates mariadb-backup.x86_64 3:10.11.8-3.fc40 @updates mariadb-common.noarch 3:10.11.8-3.fc40 @updates mariadb-connector-c.x86_64 3.3.8-3.fc40 @fedora mariadb-connector-c-config.noarch 3.3.8-3.fc40 @fedora mariadb-cracklib-password-check.x86_64 3:10.11.8-3.fc40 @updates mariadb-errmsg.noarch 3:10.11.8-3.fc40 @updates mariadb-gssapi-server.x86_64 3:10.11.8-3.fc40 @updates mariadb-server.x86_64 3:10.11.8-3.fc40 @updates mariadb-server-utils.x86_64 3:10.11.8-3.fc40 @updates mysql-selinux.noarch 1.0.10-3.fc40 @fedora perl-DBD-MariaDB.x86_64 1.23-4.fc40 @fedora 3. Does a systemd journal say anything about the issue? # journalctl -xe -u mariadb -u mysqld No 4. Please check and attach the MariaDB or MySQL server log? ("/var/log/mariadb/mariadb.log" or "/var/log/mysql/mysqld.log") 5. Please check and paste your configuration here; remove sensitive information. # /usr/libexec/mysqld --print-defaults 5. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Reproducible: Always