This is an automated email from git. It was generated because a ref
change was pushed to the "chrony/chrony.git" repository.
The branch, master has been updated
via 26b51d841e4c276ab890db697c184f47873eb705 (commit)
via 5f4cbaab7e0e01c165fff657f2b53489c949fee4 (commit)
via 7a80647fb44a733ba5895898003376c319aea888 (commit)
via 14b8df37024f7d4c6270804ec64dfca45c6cad1e (commit)
via 5cb469b2049daad410c68ab28aab5c16228ee751 (commit)
from 29d7d3176d9d1b208039a9d2ca3f26bc3cc5a387 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 26b51d841e4c276ab890db697c184f47873eb705
Author: Miroslav Lichvar <mlich...@redhat.com>
Date: Thu Oct 14 12:29:47 2021 +0200
doc: improve clientloglimit description
commit 5f4cbaab7e0e01c165fff657f2b53489c949fee4
Author: Miroslav Lichvar <mlich...@redhat.com>
Date: Thu Oct 14 12:03:49 2021 +0200
ntp: optimize detection of clients using interleaved mode
Use the lowest bit of the server RX and TX timestamp as a flag
indicating RX timestamp. This allows the server to detect potential
interleaved requests without having to save all its RX timestamps. It
significantly reduces the amount of memory needed to support clients
using the interleaved mode if most of the server's clients are using the
basic mode (e.g. a public server).
Capture the TX timestamp on the first response to the request which has
the flag set to not further delay the first interleaved response.
False positives are possible with broken clients which set the origin
timestamp to something else than zero or the server RX or TX timestamp.
This causes an unnecessary RX timestamp to be saved and TX timestamp
captured and saved.
commit 7a80647fb44a733ba5895898003376c319aea888
Author: Miroslav Lichvar <mlich...@redhat.com>
Date: Thu Oct 14 11:52:21 2021 +0200
ntp: move authentication calls in transmit_packet()
Move the calls resetting and generating authentication data out of the
loop checking for unique TX timestamp. This allows the timestamps to be
manipulated after the check.
commit 14b8df37024f7d4c6270804ec64dfca45c6cad1e
Author: Miroslav Lichvar <mlich...@redhat.com>
Date: Mon Oct 11 13:27:35 2021 +0200
clientlog: separate NTP timestamps from IP addresses
Instead of keeping one pair of RX and TX timestamp for each address, add
a separate RX->TX map using an ordered circular buffer. Save the RX
timestamps as 64-bit integers and search them with a combined linear
interpolation and binary algorithm.
This enables the server to support multiple interleaved clients sharing
the same IP address (e.g. NAT) and it will allow other improvements to
be implemented later. A drawback is that a single broken client sending
interleaved requests at a high rate (without spoofing the source
address) can now prevent clients on other addresses from getting
interleaved responses.
The total number of saved timestamps does not change. It's still
determined by the clientloglimit directive. A new option may be added
later if needed. The whole buffer is allocated at once, but only on
first use to not waste memory on client-only configurations.
commit 5cb469b2049daad410c68ab28aab5c16228ee751
Author: Miroslav Lichvar <mlich...@redhat.com>
Date: Thu Oct 14 12:31:52 2021 +0200
clientlog: fix debug message for maximum number of records
-----------------------------------------------------------------------
Summary of changes:
clientlog.c | 338 +++++++++++++++++++++++++++++++++++++++++++--
clientlog.h | 7 +-
doc/chrony.conf.adoc | 9 +-
ntp_core.c | 101 +++++++-------
test/simulation/122-xleave | 12 ++
test/unit/clientlog.c | 169 ++++++++++++++++++++++-
6 files changed, 565 insertions(+), 71 deletions(-)
hooks/post-receive
--
chrony/chrony.git
--
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe"
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the
subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
