From: Feng Liu via Virtualization <virtualization@lists.linux-foundation.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Simon Horman <simon.horman@corigine.com>,
William Tu <witu@nvidia.com>,
bpf@vger.kernel.org
Subject: Re: [PATCH net v2] virtio_net: Fix error unwinding of XDP initialization
Date: Tue, 2 May 2023 15:42:13 -0400 [thread overview]
Message-ID: <a4676198-87d4-7472-425b-16fb4a39704f@nvidia.com> (raw)
In-Reply-To: <20230502143148-mutt-send-email-mst@kernel.org>
On 2023-05-02 p.m.2:32, Michael S. Tsirkin wrote:
> External email: Use caution opening links or attachments
>
>
> On Tue, May 02, 2023 at 01:41:34PM -0400, Feng Liu 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;
>>
>> 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>
>> ---
>> drivers/net/virtio_net.c | 31 +++++++++++++++++++++----------
>> 1 file changed, 21 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
>> index 8d8038538fc4..5cd78e154d14 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,27 @@ 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;
>> +
>> + /* error unwinding of xdp init */
>
> btw we don't really need this comment - it's how all
> error handling is done anyways.
> if you need to roll v3, you can drop it.
>
Will do, thx
>> +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);
>> +
>> + return err;
>> }
>>
>> static int virtnet_poll_tx(struct napi_struct *napi, int budget)
>> @@ -2305,11 +2319,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)
>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2023-05-02 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 17:41 [PATCH net v2] virtio_net: Fix error unwinding of XDP initialization Feng Liu via Virtualization
2023-05-02 18:32 ` Michael S. Tsirkin
2023-05-02 19:42 ` Feng Liu via Virtualization [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=a4676198-87d4-7472-425b-16fb4a39704f@nvidia.com \
--to=virtualization@lists.linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=feliu@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@corigine.com \
--cc=witu@nvidia.com \
--cc=xuanzhuo@linux.alibaba.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