From: patchwork-bot+netdevbpf@kernel.org
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: kuba@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, shuah@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: drv-net: iou-zcrx: wait for memory cleanup of probe run
Date: Fri, 06 Mar 2026 23:40:05 +0000 [thread overview]
Message-ID: <177284040580.92971.6197801206670271498.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260305080446.897628-2-dtatulea@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 5 Mar 2026 10:04:45 +0200 you wrote:
> The large chunks test does a probe run of iou-zcrx before it runs the
> actual test. After the probe run finishes, the context will still exist
> until the deferred io_uring teardown. When running iou-zcrx the second
> time, io_uring_register_ifq() can return -EEXIST due to the existence of
> the old context.
>
> The fix is simple: wait for the context teardown using the new
> mp_clear_wait() utility before running the second instance of iou-zcrx.
>
> [...]
Here is the summary with links:
- [net-next] selftests: drv-net: iou-zcrx: wait for memory cleanup of probe run
https://git.kernel.org/netdev/net-next/c/507ccb668f2d
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-03-06 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 8:04 [PATCH net-next] selftests: drv-net: iou-zcrx: wait for memory cleanup of probe run Dragos Tatulea
2026-03-06 23:40 ` 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=177284040580.92971.6197801206670271498.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--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 \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox