Description of problem: SELinux is preventing irqbalance from 'map' accesses on the file /etc/ld.so.cache. ***** Plugin restorecon (94.8 confidence) suggests ************************ If si desidera sistemare l'etichetta. L'etichetta predefinita di /etc/ld.so.cache dovrebbe essere ld_so_cache_t. Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly. Do # /sbin/restorecon -v /etc/ld.so.cache ***** Plugin catchall_labels (5.21 confidence) suggests ******************* If you want to allow irqbalance to have map access on the ld.so.cache file Then e' necessario modificare l'etichetta su /etc/ld.so.cache Do # semanage fcontext -a -t FILE_TYPE '/etc/ld.so.cache' dove FILE_TYPE è uno dei seguenti: fonts_t, irqbalance_exec_t, ld_so_cache_t, ld_so_t, lib_t, locale_t, prelink_exec_t, textrel_shlib_t. Successivamente, eseguire: restorecon -v '/etc/ld.so.cache' ***** Plugin catchall (1.44 confidence) suggests ************************** If si crede che irqbalance dovrebbe avere possibilità di accesso map sui ld.so.cache file in modo predefinito. Then si dovrebbe riportare il problema come bug. E' possibile generare un modulo di politica locale per consentire questo accesso. Do allow this access for now by executing: # ausearch -c 'irqbalance' --raw | audit2allow -M my-irqbalance # semodule -X 300 -i my-irqbalance.pp Additional Information: Source Context system_u:system_r:irqbalance_t:s0 Target Context system_u:object_r:etc_t:s0 Target Objects /etc/ld.so.cache [ file ] Source irqbalance Source Path irqbalance Port <Sconosciuto> Host (removed) Source RPM Packages Target RPM Packages glibc-2.26-1.fc27.1.x86_64 Policy RPM selinux-policy-3.13.1-270.fc27.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.13.0-0.rc4.git4.1.fc27.x86_64 #1 SMP Fri Aug 11 15:03:46 UTC 2017 x86_64 x86_64 Alert Count 1 First Seen 2017-08-13 13:18:08 CEST Last Seen 2017-08-13 13:18:08 CEST Local ID 1b223e09-14ec-4070-a5ee-bac207cf8027 Raw Audit Messages type=AVC msg=audit(1502623088.570:373): avc: denied { map } for pid=635 comm="irqbalance" path="/etc/ld.so.cache" dev="sda4" ino=787090 scontext=system_u:system_r:irqbalance_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=file permissive=0 Hash: irqbalance,irqbalance_t,etc_t,file,map Version-Release number of selected component: selinux-policy-3.13.1-270.fc27.noarch Additional info: component: selinux-policy reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.13.0-0.rc4.git4.1.fc27.x86_64 type: libreport
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.