Bug 1640261

Summary: SELinux is preventing tlp from 'write' accesses on the file lock_tlp.
Product: [Fedora] Fedora Reporter: Michael <michael.scheiffler>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: dwalsh, justin.smestad, lvrabec, mgrepl, plautrba, timur.kristof
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:0fe6c4e97436995837796a159e94e5bf41eeff550034b3d27b5762ed6d084fbd;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-04 16:22:45 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:

Description Michael 2018-10-17 17:20:55 UTC
Description of problem:
SELinux is preventing tlp from 'write' accesses on the file lock_tlp.

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

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

Additional Information:
Source Context                system_u:system_r:tlp_t:s0
Target Context                system_u:object_r:var_run_t:s0
Target Objects                lock_tlp [ file ]
Source                        tlp
Source Path                   tlp
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.14.2-40.fc29.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.18.14-300.fc29.x86_64 #1 SMP Mon
                              Oct 15 13:13:16 UTC 2018 x86_64 x86_64
Alert Count                   2
First Seen                    2018-10-17 19:19:07 CEST
Last Seen                     2018-10-17 19:19:07 CEST
Local ID                      3364af13-4152-42cc-bb86-652624666dc5

Raw Audit Messages
type=AVC msg=audit(1539796747.47:293): avc:  denied  { write } for  pid=11100 comm="tlp" name="lock_tlp" dev="tmpfs" ino=40620 scontext=system_u:system_r:tlp_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=file permissive=0


Hash: tlp,tlp_t,var_run_t,file,write

Version-Release number of selected component:
selinux-policy-3.14.2-40.fc29.noarch

Additional info:
component:      selinux-policy
reporter:       libreport-2.9.6
hashmarkername: setroubleshoot
kernel:         4.18.14-300.fc29.x86_64
type:           libreport

Potential duplicate: bug 1510249

Comment 1 Timur Kristóf 2018-10-18 14:21:40 UTC
Description of problem:
This just randomly pops up on my laptop sometimes. I think it sounds reasonable to allow tlp to access this file.

Version-Release number of selected component:
selinux-policy-3.14.2-37.fc29.noarch

Additional info:
reporter:       libreport-2.9.6
hashmarkername: setroubleshoot
kernel:         4.19.0-0.rc7.git3.2.fc30.x86_64
type:           libreport

Comment 2 Timur Kristóf 2018-10-24 13:46:52 UTC
Description of problem:
This just started to occasionally pop up after I upgraded to F29. But sounds like tlp should be able to access its lock_tlp file.

Version-Release number of selected component:
selinux-policy-3.14.2-40.fc29.noarch

Additional info:
reporter:       libreport-2.9.6
hashmarkername: setroubleshoot
kernel:         4.18.16-300.fc29.x86_64
type:           libreport

Comment 3 Lukas Vrabec 2018-11-04 16:22:45 UTC

*** This bug has been marked as a duplicate of bug 1645313 ***

Comment 4 Michael 2019-03-02 11:51:29 UTC
*** Bug 1684775 has been marked as a duplicate of this bug. ***