From: patchwork-bot+netdevbpf@kernel.org
To: Parav Pandit <parav@nvidia.com>
Cc: mst@redhat.com, jasowang@redhat.com, davem@davemloft.net,
kuba@kernel.org, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com,
virtualization@lists.linux-foundation.org, bpf@vger.kernel.org,
jiri@nvidia.com
Subject: Re: [PATCH net] virtio-net: Keep stop() to follow mirror sequence of open()
Date: Thu, 02 Feb 2023 18:40:18 +0000 [thread overview]
Message-ID: <167536321823.25597.8843231088596715068.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230202163516.12559-1-parav@nvidia.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 2 Feb 2023 18:35:16 +0200 you wrote:
> Cited commit in fixes tag frees rxq xdp info while RQ NAPI is
> still enabled and packet processing may be ongoing.
>
> Follow the mirror sequence of open() in the stop() callback.
> This ensures that when rxq info is unregistered, no rx
> packet processing is ongoing.
>
> [...]
Here is the summary with links:
- [net] virtio-net: Keep stop() to follow mirror sequence of open()
https://git.kernel.org/netdev/net/c/63b114042d8a
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:[~2023-02-02 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 16:35 [PATCH net] virtio-net: Keep stop() to follow mirror sequence of open() Parav Pandit
2023-02-02 16:35 ` Parav Pandit via Virtualization
2023-02-02 18: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=167536321823.25597.8843231088596715068.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=jasowang@redhat.com \
--cc=jiri@nvidia.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=virtualization@lists.linux-foundation.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.