From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: "xuanzhuo@linux.alibaba.com" <xuanzhuo@linux.alibaba.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH net] virtio-net: set queues after driver_ok
Date: Wed, 9 Aug 2023 02:50:54 -0400 [thread overview]
Message-ID: <20230809025039-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEvETiKpx3-EsVejLe9EkSroaoFjJkLBEMmh71YU+1GjGA@mail.gmail.com>
On Wed, Aug 09, 2023 at 02:45:17PM +0800, Jason Wang wrote:
> On Wed, Aug 9, 2023 at 2:23 PM Dragos Tatulea <dtatulea@nvidia.com> wrote:
> >
> > On Tue, 2023-08-08 at 23:13 -0400, Jason Wang wrote:
> > > Commit 25266128fe16 ("virtio-net: fix race between set queues and
> > > probe") tries to fix the race between set queues and probe by calling
> > > _virtnet_set_queues() before DRIVER_OK is set. This violates virtio
> > > spec. Fixing this by setting queues after virtio_device_ready().
> > >
> > > Fixes: 25266128fe16 ("virtio-net: fix race between set queues and probe")
> > > Reported-by: Dragos Tatulea <dtatulea@nvidia.com>
> > > Signed-off-by: Jason Wang <jasowang@redhat.com>
> > > ---
> > > The patch is needed for -stable.
> > > ---
> > > drivers/net/virtio_net.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> > > index 1270c8d23463..ff03921e46df 100644
> > > --- a/drivers/net/virtio_net.c
> > > +++ b/drivers/net/virtio_net.c
> > > @@ -4219,8 +4219,6 @@ static int virtnet_probe(struct virtio_device *vdev)
> > > if (vi->has_rss || vi->has_rss_hash_report)
> > > virtnet_init_default_rss(vi);
> > >
> > > - _virtnet_set_queues(vi, vi->curr_queue_pairs);
> > > -
> > > /* serialize netdev register + virtio_device_ready() with ndo_open()
> > > */
> > > rtnl_lock();
> > >
> > > @@ -4233,6 +4231,8 @@ static int virtnet_probe(struct virtio_device *vdev)
> > >
> > > virtio_device_ready(vdev);
> > >
> > > + _virtnet_set_queues(vi, vi->curr_queue_pairs);
> > > +
> > > /* a random MAC address has been assigned, notify the device.
> > > * We don't fail probe if VIRTIO_NET_F_CTRL_MAC_ADDR is not there
> > > * because many devices work fine without getting MAC explicitly
> >
> > Thanks for the quick fix. Doesn't this fix though bring back the original race
> > that was fixed in commit 25266128fe16 ("virtio-net: fix race between set queues
> > and probe")? Or is being under the same rntl_lock session as register_netdev
> > enough to avoid the race?
>
> Yes, rtnl needs to be held for userspace requests to change the number
> of queues. So we are serialized in this way.
>
> Thanks
maybe post v2 adding this in the commit log.
> >
> > Thanks,
> > Dragos
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Dragos Tatulea <dtatulea@nvidia.com>,
"xuanzhuo@linux.alibaba.com" <xuanzhuo@linux.alibaba.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"edumazet@google.com" <edumazet@google.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net] virtio-net: set queues after driver_ok
Date: Wed, 9 Aug 2023 02:50:54 -0400 [thread overview]
Message-ID: <20230809025039-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEvETiKpx3-EsVejLe9EkSroaoFjJkLBEMmh71YU+1GjGA@mail.gmail.com>
On Wed, Aug 09, 2023 at 02:45:17PM +0800, Jason Wang wrote:
> On Wed, Aug 9, 2023 at 2:23 PM Dragos Tatulea <dtatulea@nvidia.com> wrote:
> >
> > On Tue, 2023-08-08 at 23:13 -0400, Jason Wang wrote:
> > > Commit 25266128fe16 ("virtio-net: fix race between set queues and
> > > probe") tries to fix the race between set queues and probe by calling
> > > _virtnet_set_queues() before DRIVER_OK is set. This violates virtio
> > > spec. Fixing this by setting queues after virtio_device_ready().
> > >
> > > Fixes: 25266128fe16 ("virtio-net: fix race between set queues and probe")
> > > Reported-by: Dragos Tatulea <dtatulea@nvidia.com>
> > > Signed-off-by: Jason Wang <jasowang@redhat.com>
> > > ---
> > > The patch is needed for -stable.
> > > ---
> > > drivers/net/virtio_net.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> > > index 1270c8d23463..ff03921e46df 100644
> > > --- a/drivers/net/virtio_net.c
> > > +++ b/drivers/net/virtio_net.c
> > > @@ -4219,8 +4219,6 @@ static int virtnet_probe(struct virtio_device *vdev)
> > > if (vi->has_rss || vi->has_rss_hash_report)
> > > virtnet_init_default_rss(vi);
> > >
> > > - _virtnet_set_queues(vi, vi->curr_queue_pairs);
> > > -
> > > /* serialize netdev register + virtio_device_ready() with ndo_open()
> > > */
> > > rtnl_lock();
> > >
> > > @@ -4233,6 +4231,8 @@ static int virtnet_probe(struct virtio_device *vdev)
> > >
> > > virtio_device_ready(vdev);
> > >
> > > + _virtnet_set_queues(vi, vi->curr_queue_pairs);
> > > +
> > > /* a random MAC address has been assigned, notify the device.
> > > * We don't fail probe if VIRTIO_NET_F_CTRL_MAC_ADDR is not there
> > > * because many devices work fine without getting MAC explicitly
> >
> > Thanks for the quick fix. Doesn't this fix though bring back the original race
> > that was fixed in commit 25266128fe16 ("virtio-net: fix race between set queues
> > and probe")? Or is being under the same rntl_lock session as register_netdev
> > enough to avoid the race?
>
> Yes, rtnl needs to be held for userspace requests to change the number
> of queues. So we are serialized in this way.
>
> Thanks
maybe post v2 adding this in the commit log.
> >
> > Thanks,
> > Dragos
next prev parent reply other threads:[~2023-08-09 6:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 3:13 [PATCH net] virtio-net: set queues after driver_ok Jason Wang
2023-08-09 3:13 ` Jason Wang
2023-08-09 6:22 ` Dragos Tatulea via Virtualization
2023-08-09 6:22 ` Dragos Tatulea
2023-08-09 6:45 ` Jason Wang
2023-08-09 6:45 ` Jason Wang
2023-08-09 6:50 ` Michael S. Tsirkin [this message]
2023-08-09 6:50 ` Michael S. Tsirkin
2023-08-10 3:11 ` Jason Wang
2023-08-10 3:11 ` Jason Wang
2023-08-09 6:40 ` Michael S. Tsirkin
2023-08-09 6:40 ` Michael S. Tsirkin
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=20230809025039-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xuanzhuo@linux.alibaba.com \
/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.