On Wed, Nov 23, 2022 at 03:50:30PM -0800, davidjm via Linuxptp-devel wrote: > Set the timer only when an event causes the port to transition to the > FAULTY state, rather than potentially re-arming the timeout when an > event occurs while the port was already FAULTY. > > Concretely this occurs when a port is in fault, perhaps due to a > single time out while polling for tx-timestamp. If any other port in the > system (including unrelated ones ptp4l does not even know about) cause > netlink messages to be sent. As it stands, clock_poll() will note that > the port is in fault (from before, not due to the current event) and > reset the timeout to its original value. > > If such unrelated netlink messages arrive at a regular enough cadence > the timeout may be repeatedly reset, not trigger on time (if at all) and > the port may not get a chance to clear its fault, perhaps indefinitely. > > Signed-off-by: David Mirabito <davi...@arista.com>
Applied. Thanks, Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
