From: patchwork-bot+netdevbpf@kernel.org
To: Brian Grech <bgrech@redhat.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org, horms@kernel.org,
sjpark@amazon.de, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net v3] selftests/net: fin_ack_lat: fix latency threshold typo
Date: Mon, 10 Aug 2026 23:10:15 +0000 [thread overview]
Message-ID: <178640341588.247552.5360700378574412484.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260806151645.4172900-1-bgrech@redhat.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 6 Aug 2026 10:16:45 -0500 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [net,v3] selftests/net: fin_ack_lat: fix latency threshold typo
https://git.kernel.org/netdev/net-next/c/2373107782a9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-10 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 14:59 [PATCH] selftests/net: fin_ack_lat: fix latency threshold typo Brian Grech
2026-08-04 22:01 ` Brian Grech
2026-08-06 13:30 ` Simon Horman
2026-08-06 15:01 ` Brian Grech
2026-08-06 15:16 ` [PATCH net v3] " Brian Grech
2026-08-10 23:10 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178640341588.247552.5360700378574412484.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bgrech@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=sjpark@amazon.de \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.