The FIN-ACK latency threshold was written as 100000 (100ms) instead of the intended 1000000 (1 second). Connections completing between 100ms and 1 second were incorrectly flagged as high-latency outliers and printed as failures on loaded systems.
Add the missing zero to restore the intended 1 second threshold. Signed-off-by: Brian Grech <[email protected]> --- tools/testing/selftests/net/fin_ack_lat.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftests/net/fin_ack_lat.c b/tools/testing/selftests/net/fin_ack_lat.c index 70187494b57a..4117332eb1a9 100644 --- a/tools/testing/selftests/net/fin_ack_lat.c +++ b/tools/testing/selftests/net/fin_ack_lat.c @@ -69,7 +69,7 @@ static void client(int port) lat = timediff(start, end); sum_lat += lat; nr_lat++; - if (lat < 100000) + if (lat < 1000000) goto close; if (getsockname(sock, (struct sockaddr *)&laddr, &len) == -1) -- 2.55.0
