From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
To: Feng Liu <feliu@nvidia.com>
Cc: Jason Wang <jasowang@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Simon Horman <simon.horman@corigine.com>,
Bodong Wang <bodong@nvidia.com>, William Tu <witu@nvidia.com>,
Parav Pandit <parav@nvidia.com>,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH net v3] virtio_net: Fix error unwinding of XDP initialization
Date: Mon, 8 May 2023 09:45:51 +0800 [thread overview]
Message-ID: <1683510351.569717-1-xuanzhuo@linux.alibaba.com> (raw)
In-Reply-To: <559ad341-2278-5fad-6805-c7f632e9894e@nvidia.com>
On Sat, 6 May 2023 08:08:02 -0400, Feng Liu <feliu@nvidia.com> wrote:
>
>
> On 2023-05-05 p.m.10:33, Xuan Zhuo wrote:
> > External email: Use caution opening links or attachments
> >
> >
> > On Tue, 2 May 2023 20:35:25 -0400, Feng Liu <feliu@nvidia.com> wrote:
> >> When initializing XDP in virtnet_open(), some rq xdp initialization
> >> may hit an error causing net device open failed. However, previous
> >> rqs have already initialized XDP and enabled NAPI, which is not the
> >> expected behavior. Need to roll back the previous rq initialization
> >> to avoid leaks in error unwinding of init code.
> >>
> >> Also extract a helper function of disable queue pairs, and use newly
> >> introduced helper function in error unwinding and virtnet_close;
> >>
> >> Issue: 3383038
> >> Fixes: 754b8a21a96d ("virtio_net: setup xdp_rxq_info")
> >> Signed-off-by: Feng Liu <feliu@nvidia.com>
> >> Reviewed-by: William Tu <witu@nvidia.com>
> >> Reviewed-by: Parav Pandit <parav@nvidia.com>
> >> Reviewed-by: Simon Horman <simon.horman@corigine.com>
> >> Acked-by: Michael S. Tsirkin <mst@redhat.com>
> >> Change-Id: Ib4c6a97cb7b837cfa484c593dd43a435c47ea68f
> >> ---
> >> drivers/net/virtio_net.c | 30 ++++++++++++++++++++----------
> >> 1 file changed, 20 insertions(+), 10 deletions(-)
> >>
> >> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> >> index 8d8038538fc4..3737cf120cb7 100644
> >> --- a/drivers/net/virtio_net.c
> >> +++ b/drivers/net/virtio_net.c
> >> @@ -1868,6 +1868,13 @@ static int virtnet_poll(struct napi_struct *napi, int budget)
> >> return received;
> >> }
> >>
> >> +static void virtnet_disable_qp(struct virtnet_info *vi, int qp_index)
> >> +{
> >> + virtnet_napi_tx_disable(&vi->sq[qp_index].napi);
> >> + napi_disable(&vi->rq[qp_index].napi);
> >> + xdp_rxq_info_unreg(&vi->rq[qp_index].xdp_rxq);
> >> +}
> >> +
> >> static int virtnet_open(struct net_device *dev)
> >> {
> >> struct virtnet_info *vi = netdev_priv(dev);
> >> @@ -1883,20 +1890,26 @@ static int virtnet_open(struct net_device *dev)
> >>
> >> err = xdp_rxq_info_reg(&vi->rq[i].xdp_rxq, dev, i, vi->rq[i].napi.napi_id);
> >> if (err < 0)
> >> - return err;
> >> + goto err_xdp_info_reg;
> >>
> >> err = xdp_rxq_info_reg_mem_model(&vi->rq[i].xdp_rxq,
> >> MEM_TYPE_PAGE_SHARED, NULL);
> >> - if (err < 0) {
> >> - xdp_rxq_info_unreg(&vi->rq[i].xdp_rxq);
> >> - return err;
> >> - }
> >> + if (err < 0)
> >> + goto err_xdp_reg_mem_model;
> >>
> >> virtnet_napi_enable(vi->rq[i].vq, &vi->rq[i].napi);
> >> virtnet_napi_tx_enable(vi, vi->sq[i].vq, &vi->sq[i].napi);
> >> }
> >>
> >> return 0;
> >> +
> >> +err_xdp_reg_mem_model:
> >> + xdp_rxq_info_unreg(&vi->rq[i].xdp_rxq);
> >> +err_xdp_info_reg:
> >> + for (i = i - 1; i >= 0; i--)
> >> + virtnet_disable_qp(vi, i);
> >
> >
> > I would to know should we handle for these:
> >
> > disable_delayed_refill(vi);
> > cancel_delayed_work_sync(&vi->refill);
> >
> >
> > Maybe we should call virtnet_close() with "i" directly.
> >
> > Thanks.
> >
> >
> Can’t use i directly here, because if xdp_rxq_info_reg fails, napi has
> not been enabled for current qp yet, I should roll back from the queue
> pairs where napi was enabled before(i--), otherwise it will hang at napi
> disable api
This is not the point, the key is whether we should handle with:
disable_delayed_refill(vi);
cancel_delayed_work_sync(&vi->refill);
Thanks.
>
> >> +
> >> + return err;
> >> }
> >>
> >> static int virtnet_poll_tx(struct napi_struct *napi, int budget)
> >> @@ -2305,11 +2318,8 @@ static int virtnet_close(struct net_device *dev)
> >> /* Make sure refill_work doesn't re-enable napi! */
> >> cancel_delayed_work_sync(&vi->refill);
> >>
> >> - for (i = 0; i < vi->max_queue_pairs; i++) {
> >> - virtnet_napi_tx_disable(&vi->sq[i].napi);
> >> - napi_disable(&vi->rq[i].napi);
> >> - xdp_rxq_info_unreg(&vi->rq[i].xdp_rxq);
> >> - }
> >> + for (i = 0; i < vi->max_queue_pairs; i++)
> >> + virtnet_disable_qp(vi, i);
> >>
> >> return 0;
> >> }
> >> --
> >> 2.37.1 (Apple Git-137.1)
> >>
next prev parent reply other threads:[~2023-05-08 1:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 0:35 Feng Liu
2023-05-03 3:14 ` Parav Pandit
2023-05-03 15:00 ` Feng Liu
2023-05-06 2:33 ` Xuan Zhuo
2023-05-06 12:08 ` Feng Liu
2023-05-08 1:45 ` Xuan Zhuo [this message]
2023-05-08 15:00 ` Feng Liu
2023-05-09 1:43 ` Xuan Zhuo
2023-05-10 5:00 ` Jason Wang
2023-05-10 11:54 ` Feng Liu
2023-05-12 1:54 ` Feng Liu
2023-05-12 3:25 ` Xuan Zhuo
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=1683510351.569717-1-xuanzhuo@linux.alibaba.com \
--to=xuanzhuo@linux.alibaba.com \
--cc=bodong@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=feliu@nvidia.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=simon.horman@corigine.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=witu@nvidia.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 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®