[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <23558074-ee4c-49ec-80fb-4be7f4adf825@nvidia.com>
Date: Mon, 1 Dec 2025 09:15:02 -0600
From: Dan Jurgens <danielj@...dia.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: netdev@...r.kernel.org, jasowang@...hat.com, pabeni@...hat.com,
virtualization@...ts.linux.dev, parav@...dia.com, shshitrit@...dia.com,
yohadt@...dia.com, xuanzhuo@...ux.alibaba.com, eperezma@...hat.com,
jgg@...pe.ca, kevin.tian@...el.com, kuba@...nel.org, andrew+netdev@...n.ch,
edumazet@...gle.com
Subject: Re: [PATCH net-next v13 05/12] virtio_net: Query and set flow filter
caps
On 11/26/25 5:31 PM, Michael S. Tsirkin wrote:
> On Wed, Nov 26, 2025 at 01:35:32PM -0600, Daniel Jurgens wrote:
>> @@ -5812,6 +6019,17 @@ static int virtnet_restore_up(struct virtio_device *vdev)
>> return err;
>> }
>>
>> + /* Initialize flow filters. Not supported is an acceptable and common
>> + * return code
>> + */
>> + rtnl_lock();
>> + err = virtnet_ff_init(&vi->ff, vi->vdev);
>> + if (err && err != -EOPNOTSUPP) {
>> + rtnl_unlock();
>> + return err;
>
> does not look like this rolls back previous
> initialization on error (probe does).
>
Thanks, I'll address it.
Have you reviewed the others? I'll wait until Wednesday morning to
resend, unless you confirm that's the only comment.
Powered by blists - more mailing lists