diff options
| author | Brian Grech <bgrech@redhat.com> | 2026-08-06 10:16:45 -0500 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-08-10 15:22:44 -0700 |
| commit | 2373107782a98ba15931a37bbd9dd46d7213e5aa (patch) | |
| tree | 764f0adf9fe25f2cc0fe09374abcb8150081e8e9 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 001b5d347d8ba39b2dccaefcc57967b18caec8fe (diff) | |
selftests/net: fin_ack_lat: fix latency threshold typo
The commit message for af8c8a450bf4 ("selftests: net: Add FIN_ACK
processing order related latency spike test") states: "if the latency
is larger than 1 second (spike), print a message". However the code
uses a threshold of 100000 us (100 ms), not 1000000 us (1 s).
The lower threshold causes false positives on slower hardware where
normal connection latency occasionally exceeds 100 ms but never
approaches the 1 s spike that indicates the actual FIN/ACK race bug.
Fix the threshold to match the documented intent.
Reviewed-by: Simon Horman <horms@kernel.org>
Signed-off-by: Brian Grech <bgrech@redhat.com>
Link: https://patch.msgid.link/20260806151645.4172900-1-bgrech@redhat.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions