Bug 1797412

Summary: denied { setsched } for pid=790 comm="boltd"
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dwalsh, grepl.miroslav, lvrabec, plautrba, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-03 08:58:04 UTC Type: Bug
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
journal none

Description Chris Murphy 2020-02-03 04:15:49 UTC
Description of problem:

Selinux causes boltd to crash during startup


Version-Release number of selected component (if applicable):
selinux-policy-3.14.5-21.fc32.noarch

How reproducible:
Always

Steps to Reproduce:
1. Boot
2.
3.

Actual results:

[   10.503066] fmac.local audit[790]: AVC avc:  denied  { setsched } for  pid=790 comm="boltd" scontext=system_u:system_r:boltd_t:s0 tcontext=system_u:system_r:boltd_t:s0 tclass=process permissive=0
[   10.503274] fmac.local audit[790]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:boltd_t:s0 pid=790 comm="boltd" exe="/usr/libexec/boltd" sig=5 res=1

...

[   11.235530] fmac.local systemd[1]: bolt.service: Main process exited, code=killed, status=5/TRAP
[   11.235858] fmac.local systemd[1]: bolt.service: Failed with result 'signal'.
[   11.236738] fmac.local systemd[1]: Failed to start Thunderbolt system service.



Expected results:

boltd shouldn't crash


Additional info:

Comment 1 Chris Murphy 2020-02-03 04:16:36 UTC
Created attachment 1657248 [details]
journal

Comment 2 Zdenek Pytela 2020-02-03 08:58:04 UTC

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