Re: No packets transmitted when using Yocto 4.3.1
Thomas Lange <[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <[email protected]> |
On 2024-01-02 12:36, Miroslav Lichvar wrote: > 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-1GrQudf0pfdn57vcNwVNVA@public.gmane.org/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. A fix for the cmsg bug has been committed into the pipeline for v6.7-rc9: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=382a32018b74 In time, it could also make it down to some LTS releases. /Thomas -- To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "unsubscribe" in the subject. For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "help" in the subject. Trouble? Email [email protected]