From: patchwork-bot+netdevbpf@kernel•org
To: Jason Wang <jasowang@redhat•com>
Cc: mst@redhat•com, xuanzhuo@linux•alibaba.com, davem@davemloft•net,
edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
virtualization@lists•linux-foundation.org,
netdev@vger•kernel.org
Subject: Re: [PATCH net] virtio-net: fix race between set queues and probe
Date: Thu, 27 Jul 2023 05:20:21 +0000 [thread overview]
Message-ID: <169043522115.2558.14440034474051213901.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230725072049.617289-1-jasowang@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Tue, 25 Jul 2023 03:20:49 -0400 you wrote:
> A race were found where set_channels could be called after registering
> but before virtnet_set_queues() in virtnet_probe(). Fixing this by
> moving the virtnet_set_queues() before netdevice registering. While at
> it, use _virtnet_set_queues() to avoid holding rtnl as the device is
> not even registered at that time.
>
> Fixes: a220871be66f ("virtio-net: correctly enable multiqueue")
> Signed-off-by: Jason Wang <jasowang@redhat•com>
>
> [...]
Here is the summary with links:
- [net] virtio-net: fix race between set queues and probe
https://git.kernel.org/netdev/net/c/25266128fe16
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-07-27 5:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 7:20 [PATCH net] virtio-net: fix race between set queues and probe Jason Wang
2023-07-25 7:53 ` Michael S. Tsirkin
2023-07-26 1:54 ` Jason Wang
2023-07-25 11:10 ` Xuan Zhuo
2023-07-27 5:20 ` patchwork-bot+netdevbpf [this message]
2023-08-08 11:35 ` Dragos Tatulea
2023-08-09 1:43 ` Jason Wang
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=169043522115.2558.14440034474051213901.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=jasowang@redhat$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=mst@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=virtualization@lists$(echo .)linux-foundation.org \
--cc=xuanzhuo@linux$(echo .)alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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