From: patchwork-bot+netdevbpf@kernel.org
To: Mohsin Bashir <mohsin.bashr@gmail.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.or,
pabeni@redhat.com, shuah@kernel.org, ast@kernel.org,
daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
sdf@fomichev.me, linux-kselftest@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: drv-net: Wait for bkg socat to start
Date: Sat, 26 Jul 2025 00:00:13 +0000 [thread overview]
Message-ID: <175348801351.3451765.3781597644210857755.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250724235140.2645885-1-mohsin.bashr@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 24 Jul 2025 16:51:40 -0700 you wrote:
> Currently, UDP exchange is prone to failure when cmd attempt to send data
> while socat in bkg is not ready. Since, the behavior is probabilistic, this
> can result in flakiness for XDP tests. While testing
> test_xdp_native_tx_mb() on netdevsim, a failure rate of around 1% in 500
> 500 iterations was observed.
>
> Use wait_port_listen() to ensure that the bkg socat is started and ready to
> receive before cmd start sending. With proposed changes, a re-run of the
> same test passed 100% of time.
>
> [...]
Here is the summary with links:
- [net-next] selftests: drv-net: Wait for bkg socat to start
https://git.kernel.org/netdev/net-next/c/d1f3dbad6f0d
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:[~2025-07-25 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 23:51 [PATCH net-next] selftests: drv-net: Wait for bkg socat to start Mohsin Bashir
2025-07-26 0:00 ` 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=175348801351.3451765.3781597644210857755.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.or \
--cc=linux-kselftest@vger.kernel.org \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@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.