Red Hat Bugzilla – Bug 1429853
ptp4l cannot respond to unconfined pmc using UDS
Last modified: 2018-04-10 08:29:13 EDT
Description of problem: When ptp4l from the linuxptp package is running, pmc doesn't get any responses from ptp4l over Unix domain socket. type=AVC msg=audit(1488880198.380:52): avc: denied { sendto } for pid=850 comm="ptp4l" path="/run/pmc.884" scontext=system_u:system_r:ptp4l_t:s0 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=unix_dgram_socket Version-Release number of selected component (if applicable): selinux-policy-3.13.1-124.el7.noarch How reproducible: Always Steps to Reproduce: 1. yum install linuxptp 1. vi /etc/sysconfig/ptp4l (e.g. OPTIONS="-f /etc/ptp4l.conf -i eth0 -S") 2. systemctl start ptp4l 3. pmc -b 0 -u 'GET TIME_STATUS_NP' Actual results: # pmc -b 0 -u 'GET TIME_STATUS_NP' sending: GET TIME_STATUS_NP Expected results: # pmc -b 0 -u 'GET TIME_STATUS_NP' sending: GET TIME_STATUS_NP 123456.1234.123456-0 seq 0 RESPONSE MANAGEMENT TIME_STATUS_NP master_offset 0 ingress_time 0 cumulativeScaledRateOffset +0.000000000 scaledLastGmPhaseChange 0 gmTimeBaseIndicator 0 lastGmPhaseChange 0x0000'0000000000000000.0000 gmPresent false gmIdentity 123456.1234.123456
Confirmed. Easy to reproduce: ---- type=PROCTITLE msg=audit(03/07/2017 05:22:39.886:416) : proctitle=/usr/sbin/ptp4l -f /etc/ptp4l.conf -i eth0 -S type=SYSCALL msg=audit(03/07/2017 05:22:39.886:416) : arch=x86_64 syscall=sendto success=yes exit=104 a0=0x13 a1=0x557a94cff8a8 a2=0x68 a3=0x0 items=0 ppid=1 pid=8991 auid=unset uid=root gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root tty=(none) ses=unset comm=ptp4l exe=/usr/sbin/ptp4l subj=system_u:system_r:ptp4l_t:s0 key=(null) type=AVC msg=audit(03/07/2017 05:22:39.886:416) : avc: denied { sendto } for pid=8991 comm=ptp4l path=/run/pmc.9019 scontext=system_u:system_r:ptp4l_t:s0 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=unix_dgram_socket permissive=1 ----
Please, change the priority/severity if not adequate.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0763