From: Laurent Vivier <lvivier@redhat.com>
To: Paolo Abeni <pabeni@redhat.com>, linux-kernel@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
virtualization@lists.linux-foundation.org,
"Cindy Lu" <lulu@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eli Cohen" <elic@nvidia.com>,
"Gautam Dawar" <gautam.dawar@xilinx.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
netdev@vger.kernel.org, "Parav Pandit" <parav@nvidia.com>
Subject: Re: [PATCH v3 2/2] virtio_net: notify MAC address change on device initialization
Date: Tue, 31 Jan 2023 10:32:52 +0100 [thread overview]
Message-ID: <8bb17aed-d643-2e33-472a-9f237e26e4d1@redhat.com> (raw)
In-Reply-To: <949500bd10077989eb21bd41d6bb1a0de296f9d8.camel@redhat.com>
On 1/31/23 10:01, Paolo Abeni wrote:
> On Fri, 2023-01-27 at 21:45 +0100, Laurent Vivier wrote:
>> In virtnet_probe(), if the device doesn't provide a MAC address the
>> driver assigns a random one.
>> As we modify the MAC address we need to notify the device to allow it
>> to update all the related information.
>>
>> The problem can be seen with vDPA and mlx5_vdpa driver as it doesn't
>> assign a MAC address by default. The virtio_net device uses a random
>> MAC address (we can see it with "ip link"), but we can't ping a net
>> namespace from another one using the virtio-vdpa device because the
>> new MAC address has not been provided to the hardware:
>> RX packets are dropped since they don't go through the receive filters,
>> TX packets go through unaffected.
>>
>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>> ---
>> drivers/net/virtio_net.c | 20 ++++++++++++++++++++
>> 1 file changed, 20 insertions(+)
>>
>> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
>> index 7d700f8e545a..704a05f1c279 100644
>> --- a/drivers/net/virtio_net.c
>> +++ b/drivers/net/virtio_net.c
>> @@ -3806,6 +3806,8 @@ static int virtnet_probe(struct virtio_device *vdev)
>> eth_hw_addr_set(dev, addr);
>> } else {
>> eth_hw_addr_random(dev);
>> + dev_info(&vdev->dev, "Assigned random MAC address %pM\n",
>> + dev->dev_addr);
>> }
>>
>> /* Set up our device-specific information */
>> @@ -3933,6 +3935,24 @@ static int virtnet_probe(struct virtio_device *vdev)
>>
>> virtio_device_ready(vdev);
>>
>> + /* 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
>> + */
>> + if (!virtio_has_feature(vdev, VIRTIO_NET_F_MAC) &&
>> + virtio_has_feature(vi->vdev, VIRTIO_NET_F_CTRL_MAC_ADDR)) {
>> + struct scatterlist sg;
>> +
>> + sg_init_one(&sg, dev->dev_addr, dev->addr_len);
>> + if (!virtnet_send_command(vi, VIRTIO_NET_CTRL_MAC,
>> + VIRTIO_NET_CTRL_MAC_ADDR_SET, &sg)) {
>> + pr_debug("virtio_net: setting MAC address failed\n");
>> + rtnl_unlock();
>> + err = -EINVAL;
>> + goto free_unregister_netdev;
>
> Since the above is still dealing with device initialization, would it
> make sense moving such init step before registering the netdevice?
It depends if we can send the command using the control command queue or not.
I don't think we can use a vq before virtio_device_ready().
Thanks,
Laurent
next prev parent reply other threads:[~2023-01-31 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 20:44 [PATCH v3 0/2] virtio_net: vdpa: update MAC address when it is generated by virtio-net Laurent Vivier
2023-01-27 20:44 ` [PATCH v3 1/2] virtio_net: disable VIRTIO_NET_F_STANDBY if VIRTIO_NET_F_MAC is not set Laurent Vivier
2023-01-31 22:09 ` Michael S. Tsirkin
2023-01-27 20:45 ` [PATCH v3 2/2] virtio_net: notify MAC address change on device initialization Laurent Vivier
2023-01-31 9:01 ` Paolo Abeni
2023-01-31 9:32 ` Laurent Vivier [this message]
2023-01-31 11:41 ` Paolo Abeni
2023-01-31 13:43 ` Michael S. Tsirkin
2023-01-31 14:40 ` Paolo Abeni
2023-01-31 22:09 ` Michael S. Tsirkin
2023-02-02 5:00 ` [PATCH v3 0/2] virtio_net: vdpa: update MAC address when it is generated by virtio-net patchwork-bot+netdevbpf
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=8bb17aed-d643-2e33-472a-9f237e26e4d1@redhat.com \
--to=lvivier@redhat.com \
--cc=davem@davemloft.net \
--cc=elic@nvidia.com \
--cc=eperezma@redhat.com \
--cc=gautam.dawar@xilinx.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®