On Tue, Jan 02, 2024 at 11:54:32AM +0100, Thomas Lange wrote: > AFAICT this bug breaks timestamping via cmsg (i.e. Chrony) for all > 32bit platforms using 64bit time. There could be other cases when > SO_TIMESTAMPING is mapped to SO_TIMESTAMPING_NEW though. I haven't > looked into that.
Do you know if this includes the "legacy" (bullseye, 32 bit) Raspbian? -- Ian -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
