[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACGkMEt2SEWY-hUKv2=PwLZr+NNGSobr4i-XQ_qDtGk+tNw8Gw@mail.gmail.com>
Date: Wed, 12 Nov 2025 09:00:22 +0800
From: Jason Wang <jasowang@...hat.com>
To: Paolo Abeni <pabeni@...hat.com>
Cc: Daniel Jurgens <danielj@...dia.com>, netdev@...r.kernel.org, mst@...hat.com,
virtualization@...ts.linux.dev, parav@...dia.com, shshitrit@...dia.com,
yohadt@...dia.com, xuanzhuo@...ux.alibaba.com, eperezma@...hat.com,
shameerali.kolothum.thodi@...wei.com, jgg@...pe.ca, kevin.tian@...el.com,
kuba@...nel.org, andrew+netdev@...n.ch, edumazet@...gle.com
Subject: Re: [PATCH net-next v9 05/12] virtio_net: Query and set flow filter caps
On Tue, Nov 11, 2025 at 6:42 PM Paolo Abeni <pabeni@...hat.com> wrote:
>
> On 11/7/25 5:15 AM, Daniel Jurgens wrote:
> > @@ -7121,6 +7301,15 @@ static int virtnet_probe(struct virtio_device *vdev)
> > }
> > vi->guest_offloads_capable = vi->guest_offloads;
> >
> > + /* Initialize flow filters. Not supported is an acceptable and common
> > + * return code
> > + */
> > + err = virtnet_ff_init(&vi->ff, vi->vdev);
> > + if (err && err != -EOPNOTSUPP) {
> > + rtnl_unlock();
> > + goto free_unregister_netdev;
>
> I'm sorry for not noticing the following earlier, but it looks like that
> the code could error out on ENOMEM even if the feature is not really
> supported, when `cap_id_list` allocation fails, which in turn looks a
> bit bad, as the allocated chunk is not that small (32K if I read
> correctly).
>
> @Jason, @Micheal: WDYT?
I agree. I think virtnet_ff_init() should be only called when the
feature is negotiated.
Thanks
>
> /P
>
Powered by blists - more mailing lists