faraphel/chrony
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ntp: don't capture TX timestamps if clientlog is disabled

Browse source 
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: 5f4cbaab7e ("ntp: optimize detection of clients using interleaved mode")
This commit is contained in:
Miroslav Lichvar 2021-10-18 11:29:58 +02:00
parent 26b51d841e
commit 61226cda8c
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
ntp_core.c
View file

@ -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 transmit timestamp (this is verified in transmit_packet()). For a new
client starting with a zero origin timestamp, the third response is the client starting with a zero origin timestamp, the third response is the
earliest one that can be interleaved. */ 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) { UTI_CompareNtp64(&message->receive_ts, &message->transmit_ts) != 0) {
ntp_rx = message->originate_ts; ntp_rx = message->originate_ts;
local_ntp_rx = &ntp_rx; local_ntp_rx = &ntp_rx;