From 61226cda8cdfa343b1c1b44b65e8a6977c5b5580 Mon Sep 17 00:00:00 2001 From: Miroslav Lichvar Date: Mon, 18 Oct 2021 11:29:58 +0200 Subject: [PATCH] ntp: don't capture TX timestamps if clientlog is disabled When responding to a request, don't waste time with TX timestamping if the timestamp will not be saved (i.e. clientlog is disabled). Fixes: 5f4cbaab7e0e ("ntp: optimize detection of clients using interleaved mode") --- ntp_core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ntp_core.c b/ntp_core.c index 0a5cd44..7991299 100644 --- a/ntp_core.c +++ b/ntp_core.c @@ -2125,7 +2125,7 @@ NCR_ProcessRxUnknown(NTP_Remote_Address *remote_addr, NTP_Local_Address *local_a transmit timestamp (this is verified in transmit_packet()). For a new client starting with a zero origin timestamp, the third response is the earliest one that can be interleaved. */ - if (kod == 0 && message->originate_ts.lo & htonl(1) && + if (kod == 0 && log_index >= 0 && message->originate_ts.lo & htonl(1) && UTI_CompareNtp64(&message->receive_ts, &message->transmit_ts) != 0) { ntp_rx = message->originate_ts; local_ntp_rx = &ntp_rx;