From: Laurent Vivier <lvivier@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Cindy Lu" <lulu@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
"Eugenio Pérez" <eperezma@redhat.com>,
"Eli Cohen" <elic@nvidia.com>,
"Gautam Dawar" <gautam.dawar@xilinx.com>
Subject: Re: [PATCH 0/4] virtio_net: vdpa: update MAC address when it is generated by virtio-net
Date: Mon, 23 Jan 2023 10:25:44 +0100 [thread overview]
Message-ID: <aa07f74e-ad9e-bc94-9ace-257db0aa5b4d@redhat.com> (raw)
In-Reply-To: <20230122052211-mutt-send-email-mst@kernel.org>
On 1/22/23 11:23, Michael S. Tsirkin wrote:
> On Sun, Jan 22, 2023 at 11:05:22AM +0100, Laurent Vivier wrote:
>> When the MAC address is not provided by the vdpa device virtio_net
>> driver assigns a random one without notifying the device.
>> The consequence, in the case of mlx5_vdpa, is the internal routing
>> tables of the device are not updated and this can block the
>> communication between two namespaces.
>>
>> To fix this problem, use virtnet_send_command(VIRTIO_NET_CTRL_MAC)
>> to set the address from virtnet_probe() when the MAC address is
>> randomly assigned from virtio_net.
>>
>> While I was testing this change I found 3 other bugs in vdpa_sim_net:
>>
>> - vdpa_sim_net sets the VIRTIO_NET_F_MAC even if no MAC address is
>> provided. So virtio_net doesn't generate a random MAC address and
>> the MAC address appears to be 00:00:00:00:00:00
>>
>> - vdpa_sim_net never processes the command and virtnet_send_command()
>> hangs in an infinite loop. To avoid a kernel crash add a timeout
>> in the loop.
>>
>> - To allow vdpa_sim_net to process the command, replace the cpu_relax()
>> in the loop by a schedule(). vdpa_sim_net uses a workqueue to process
>> the queue, and if we don't allow the kernel to schedule, the queue
>> is not processed and the loop is infinite.
>
> I'd split these things out as opposed to a series unless there's
> a dependency I missed.
We needed to fix virtio_net before fixing vdpa_sim_net otherwise the
virtnet_send_command() hangs when we define the vdpa device with "vdpa dev" but without a
MAC address.
> All this reminds me of
> https://lore.kernel.org/r/20221226074908.8154-5-jasowang%40redhat.com
>
> how is this patch different/better?
> Pls also CC people involved in that original discussion.
I was not aware of the Jason's series.
It seems to address better the problem, except it triggers the ASSERT_RTNL() in
virtnet_send_command() when it is called from virtnet_probe().
I will remove patches 2 and 4 from my series.
PATCH 3 can be sent on independently too.
Thanks,
Laurent
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2023-01-23 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 10:05 [PATCH 0/4] virtio_net: vdpa: update MAC address when it is generated by virtio-net Laurent Vivier
2023-01-22 10:05 ` [PATCH 1/4] virtio_net: notify MAC address change on device initialization Laurent Vivier
[not found] ` <07a24753-767b-4e1e-2bcf-21ec04bc044a@nvidia.com>
2023-01-23 9:52 ` Laurent Vivier
[not found] ` <20230123193114.56aaec3a@kernel.org>
2023-01-24 7:19 ` Laurent Vivier
2023-01-22 10:05 ` [PATCH 2/4] virtio_net: add a timeout in virtnet_send_command() Laurent Vivier
2023-01-22 10:05 ` [PATCH 3/4] vdpa_sim_net: don't always set VIRTIO_NET_F_MAC Laurent Vivier
2023-01-22 10:05 ` [PATCH 4/4] virtio_net: fix virtnet_send_command() with vdpa_sim_net Laurent Vivier
2023-01-22 10:23 ` [PATCH 0/4] virtio_net: vdpa: update MAC address when it is generated by virtio-net Michael S. Tsirkin
2023-01-23 9:25 ` Laurent Vivier [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=aa07f74e-ad9e-bc94-9ace-257db0aa5b4d@redhat.com \
--to=lvivier@redhat.com \
--cc=davem@davemloft.net \
--cc=elic@nvidia.com \
--cc=eperezma@redhat.com \
--cc=gautam.dawar@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).