| Re: [chrony-users] No packets transmitted when using Yocto 4.3.1 |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] No packets transmitted when using Yocto 4.3.1
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 2 Jan 2024 12:36:12 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1704195373; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=L6mjEQboOlnM9JXmEsrmcnV/CvTu3hH4Pshb74os11k=; b=ZKbo24K68Kw+L07doHt0QMDIRY2BWyp71YE1fDdFwW4QPUrlK0x1l+FDv5Wxkede6jfH0K N35l8fc2D8aulGfZKGQ0HfyM5DXi+45wufbN0a2N1j3Mgq03hw9g3QJJ0hGXjD+enhDyeN OJjkAT7TjYb23Z9sDqXqZggRuBUumBo=
On Tue, Jan 02, 2024 at 11:54:32AM +0100, Thomas Lange wrote:
> The root cause is a kernel bug. I have reported it to netdev:
>
> https://lore.kernel.org/netdev/a9090be2-ca7c-494c-89cb-49b1db2438ba@xxxxxxxxxxxx/T/#u
>
> A proper patch has not been committed yet though, but it seems that my
> one-line fix should do it according to comments so far.
Interesting. Thanks for looking into it.
> AFAICT this bug breaks timestamping via cmsg (i.e. Chrony) for all 32bit
> platforms using 64bit time.
Yes, it seems so. I can reproduce it on OpenWrt, now that I know what
to look for.
It doesn't impact all NTP packets. chronyd should not use the cmsg in
server basic mode and both client modes unless the acquisitionport
directive is used.
The cmsg use in chronyd is limited to kernel versions >= 4.8. Maybe we
should extend that up to the current version for the case when 64-bit
time_t is used on a 32-bit arch.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.