Bug 1416611

Summary: SELinux is preventing ps from 'sys_ptrace' accesses on the cap_userns Unknown.
Product: [Fedora] Fedora Reporter: David Sirrine <dsirrine>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: dominick.grift, dwalsh, lvrabec, mgrepl, paul.destefano-redhat2, plautrba, pmoore, ssekidde
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6f5a5f91bdae496d833d83aabe753892a69beca2a008e79f62c033fd6e4c0bfa;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:45:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description David Sirrine 2017-01-26 02:02:19 UTC
Description of problem:
1) Installed pcp on Fedora 25 system
2) systemctl enable pmcd
3) systemctl enable pmlogger
4) systemctl start pmcd
5) systemctl start pmlogger
SELinux is preventing ps from 'sys_ptrace' accesses on the cap_userns Unknown.

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

If you believe that ps should be allowed sys_ptrace access on the Unknown cap_userns by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
allow this access for now by executing:
# ausearch -c 'ps' --raw | audit2allow -M my-ps
# semodule -X 300 -i my-ps.pp

Additional Information:
Source Context                system_u:system_r:pcp_pmlogger_t:s0
Target Context                system_u:system_r:pcp_pmlogger_t:s0
Target Objects                Unknown [ cap_userns ]
Source                        ps
Source Path                   ps
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-225.6.fc25.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.9.5-200.fc25.x86_64 #1 SMP Fri
                              Jan 20 12:24:16 UTC 2017 x86_64 x86_64
Alert Count                   18
First Seen                    2017-01-25 20:59:48 EST
Last Seen                     2017-01-25 20:59:51 EST
Local ID                      487729ab-833b-43f6-a320-f048e690fd1c

Raw Audit Messages
type=AVC msg=audit(1485395991.310:434): avc:  denied  { sys_ptrace } for  pid=8034 comm="ps" capability=19  scontext=system_u:system_r:pcp_pmlogger_t:s0 tcontext=system_u:system_r:pcp_pmlogger_t:s0 tclass=cap_userns permissive=0

Hash: ps,pcp_pmlogger_t,pcp_pmlogger_t,cap_userns,sys_ptrace

Version-Release number of selected component:

Additional info:
reporter:       libreport-2.8.0
hashmarkername: setroubleshoot
kernel:         4.9.5-200.fc25.x86_64
type:           libreport

Comment 1 Paul DeStefano 2017-01-29 19:03:17 UTC
Me too, but slightly different hash.  Nothing to do with pcp, just md.  Happens once a week at same time.

SELinux is preventing ps from sys_ptrace access on the cap_userns Unknown.

Raw Audit Messages
type=AVC msg=audit(1485680407.955:26731): avc:  denied  { sys_ptrace } for  pid=3352 comm="ps" capability=19  scontext=system_u:system_r:mdadm_t:s0-s0:c0.c1023 tcontext=system_u:system_r:mdadm_t:s0-s0:c0.c1023 tclass=cap_userns permissive=0

Hash: ps,mdadm_t,mdadm_t,cap_userns,sys_ptrace

Should this be a different bug?

Comment 2 Fedora End Of Life 2017-11-16 19:59:37 UTC
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.

Comment 3 Paul DeStefano 2017-11-24 22:28:54 UTC
Well, I see this alert on F26. Last occurred: 8 Oct 2017.  So, it clearly didn't die with F25.

Comment 4 Fedora End Of Life 2017-12-12 10:45:10 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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

Thank you for reporting this bug and we are sorry it could not be fixed.