On Wed, Apr 26, 2023 at 02:44:27PM +0200, Miroslav Lichvar wrote:
> When the netlink socket of a port (used for receiving link up/down
> events) had an error (e.g. ENOBUFS due to the kernel sending too many
> messages), ptp4l switched the port to the faulty state, but it kept
> getting POLLERR on t
When the netlink socket of a port (used for receiving link up/down
events) had an error (e.g. ENOBUFS due to the kernel sending too many
messages), ptp4l switched the port to the faulty state, but it kept
getting POLLERR on the socket and logged "port 1: unexpected socket
error" in an infinite loop
