| [chrony-dev] Is 124-tai too sensitive? |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-dev] Is 124-tai too sensitive?
- From: Reinhard Max <max@xxxxxxx>
- Date: Wed, 29 May 2024 16:30:10 +0200
- Authentication-results: smtp-out1.suse.de; dkim=pass header.d=suse.de header.s=susede2_rsa header.b=EPoilNpF; dkim=pass header.d=suse.de header.s=susede2_ed25519 header.b=qZ8VaYQ1
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1716993010; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=0p7AgGGx7x/QHO625p1MmouNTOWP5AtEwHlkoF93YPY=; b=EPoilNpFvo8h0gK0Y5fVpJShLHq7GLNMhKD86jVd3uNxvROxKKEycuq/R+EdMsWKe4tQQ/ +fzKlQXm19AmaDYOgTGeNtNcVWhvea7UrMH7VP26HxZ5YuP5VLTpVavmcmG5EV2f7uibMf KWtoRlUGj8DJsq7jNnBmUVa7hjVnS3E=
- Dkim-signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1716993010; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=0p7AgGGx7x/QHO625p1MmouNTOWP5AtEwHlkoF93YPY=; b=qZ8VaYQ1slFpEqlapZ1g576/6w8/SOF5e2rBQufpcXn7X2nHmJG4tHA9T2PK46zcI5fnq4 WuDTtFvuoqdXdKBg==
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1716993010; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=0p7AgGGx7x/QHO625p1MmouNTOWP5AtEwHlkoF93YPY=; b=EPoilNpFvo8h0gK0Y5fVpJShLHq7GLNMhKD86jVd3uNxvROxKKEycuq/R+EdMsWKe4tQQ/ +fzKlQXm19AmaDYOgTGeNtNcVWhvea7UrMH7VP26HxZ5YuP5VLTpVavmcmG5EV2f7uibMf KWtoRlUGj8DJsq7jNnBmUVa7hjVnS3E=
- Dkim-signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1716993010; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=0p7AgGGx7x/QHO625p1MmouNTOWP5AtEwHlkoF93YPY=; b=qZ8VaYQ1slFpEqlapZ1g576/6w8/SOF5e2rBQufpcXn7X2nHmJG4tHA9T2PK46zcI5fnq4 WuDTtFvuoqdXdKBg==
Hi,
we see 124-tai frequently fail on architectures like ppc64le and
aarch64, but not on x86_64.
The failure happens in is_offset_ok() in reference.c while running the
first test in 124-tai. On x86_64 fabs(offset) reaches a maximum of
~0.00098, i.e. it stays just below the 0.001 second limit set by the
test, whereas on the affected architectures it slightly exceeds the
limit in most of the test runs, e.g. to 0.0010031337 causing chronyd to
exit with an error.
I can mitigate this by increasing the allowed offset to cover that
overshoot, but I am not sure if that would be in accordance with the
intention of the test.
cu
Reinhard
--
SUSE Software Solutions Germany GmbH (HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.