Bug 1462554 - SELinux is preventing x86_energy_perf from read, write access on the chr_file msr.
SELinux is preventing x86_energy_perf from read, write access on the chr_file...
Status: NEW
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
25
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Lukas Vrabec
Fedora Extras Quality Assurance
abrt_hash:0121ef5fd889c6569f93de966e0...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-18 16:40 EDT by Riccardo Melioli
Modified: 2017-11-16 13:43 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Riccardo Melioli 2017-06-18 16:40:05 EDT
Description of problem:
SELinux is preventing x86_energy_perf from read, write access on the chr_file msr.

*****  Plugin device (91.4 confidence) suggests   ****************************

If you want to allow x86_energy_perf to have read write access on the msr chr_file
Then you need to change the label on msr to a type of a similar device.
Do
# semanage fcontext -a -t SIMILAR_TYPE 'msr'
# restorecon -v 'msr'

*****  Plugin catchall (9.59 confidence) suggests   **************************

If you believe that x86_energy_perf should be allowed read write access on the msr chr_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 'x86_energy_perf' --raw | audit2allow -M my-x86energyperf
# semodule -X 300 -i my-x86energyperf.pp

Additional Information:
Source Context                system_u:system_r:tlp_t:s0
Target Context                system_u:object_r:device_t:s0
Target Objects                msr [ chr_file ]
Source                        x86_energy_perf
Source Path                   x86_energy_perf
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-225.18.fc25.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.11.5-200.fc25.x86_64 #1 SMP Wed
                              Jun 14 17:17:29 UTC 2017 x86_64 x86_64
Alert Count                   1
First Seen                    2017-06-18 20:43:53 CEST
Last Seen                     2017-06-18 20:43:53 CEST
Local ID                      fe1198d1-d4d2-4aaa-918f-e3ac29ec62fa

Raw Audit Messages
type=AVC msg=audit(1497811433.464:562): avc:  denied  { read write } for  pid=21841 comm="x86_energy_perf" name="msr" dev="devtmpfs" ino=424578 scontext=system_u:system_r:tlp_t:s0 tcontext=system_u:object_r:device_t:s0 tclass=chr_file permissive=1


Hash: x86_energy_perf,tlp_t,device_t,chr_file,read,write

Version-Release number of selected component:
selinux-policy-3.13.1-225.18.fc25.noarch

Additional info:
reporter:       libreport-2.8.0
hashmarkername: setroubleshoot
kernel:         4.11.5-200.fc25.x86_64
type:           libreport
Comment 1 Fedora End Of Life 2017-11-16 13:43:25 EST
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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.

Note You need to log in before you can comment on or make changes to this bug.