| Re: [chrony-dev] [PATCH] sys_linux: allow clock_gettime64 in seccomp filter |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] [PATCH] sys_linux: allow clock_gettime64 in seccomp filter
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 14 May 2020 11:15:36 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1589447741; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=BpkB4LCq5TeCK3EzvYdP5eC3umZS77feEFV4uUnzlvk=; b=c3t5zCboBG+hBTJ/0NHNEo/kHoaDeuGvjEWCi8BM0VOUdZyPls8yAT2O6G+m4udGwTsV1k rzaRvRPdxDpiN3rvKqaoVtLpdZAJmLRbb4oKtt02QMlDGrdb3kQn1msKc+BZR+/hAVcD6S f8/Qdq8yencex0rB2j+xs/X+Np5mVTc=
On Thu, May 14, 2020 at 09:15:31AM +0200, Miroslav Lichvar wrote:
> On Wed, May 13, 2020 at 09:40:07PM +0200, Vincent Blut wrote:
> > Hi Miroslav,
> >
> > We got a bug reportÃ?â??Ã?¹ showing that chronyd might not start correctly, notably
> > on Raspberry Pi 2/3, when the system call filter is enabled due to the
> > clock_gettime64() syscall not being whitelisted. Patch attached!
>
> Thanks, Vincent. I'll push the patch with few others later today.
Actually, it seems the patch breaks compilation on some of my
machines. The clock_gettime64 syscall is new and supported only in the
latest two libseccomp versions, so I'd prefer if there was an ifdef
for __NR_clock_gettime64.
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.