From: zhoumin <zhoumin@loongson.cn>
To: "Xia, Chenbo" <chenbo.xia@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"maobibo@loongson.cn" <maobibo@loongson.cn>
Subject: Re: [PATCH v2] vhost: fix build
Date: Mon, 26 Sep 2022 11:25:58 +0800 [thread overview]
Message-ID: <7352946c-b313-d5ea-e2a0-6f761997594d@loongson.cn> (raw)
In-Reply-To: <SN6PR11MB35047E343988178CF14A61179C529@SN6PR11MB3504.namprd11.prod.outlook.com>
Hi Chenbo,
On Mon, 26 Sep 2022, 10:57, Xia, Chenbo wrote:
> Hi Min,
>
>> -----Original Message-----
>> From: Min Zhou <zhoumin@loongson.cn>
>> Sent: Monday, August 29, 2022 4:29 PM
>> To: david.marchand@redhat.com; maxime.coquelin@redhat.com; Xia, Chenbo
>> <chenbo.xia@intel.com>; zhoumin@loongson.cn
>> Cc: dev@dpdk.org; maobibo@loongson.cn
>> Subject: [PATCH v2] vhost: fix build
>>
>> On CentOS 8 or Debian 10.4 systems using gcc 12.1 to cross
>> compile DPDK, gcc shows a following warning which will cause
>> build to fail when build is run with -werror:
>>
>> In function 'mbuf_to_desc',
>> inlined from 'vhost_enqueue_async_packed'
>> at ../lib/vhost/virtio_net.c:1826:6,
>> inlined from 'virtio_dev_rx_async_packed'
>> at ../lib/vhost/virtio_net.c:1840:6,
>> inlined from 'virtio_dev_rx_async_submit_packed.constprop'
>> at ../lib/vhost/virtio_net.c:1900:7:
>> ../lib/vhost/virtio_net.c:1161:35: error: 'buf_vec[0].buf_len' may be used
>> uninitialized [-Werror=maybe-uninitialized]
>> 1161 | buf_len = buf_vec[vec_idx].buf_len;
>> | ~~~~~~~~~~~~~~~~^~~~~~~~
>> ../lib/vhost/virtio_net.c: In function
>> 'virtio_dev_rx_async_submit_packed.constprop':
>> ../lib/vhost/virtio_net.c:1838:27: note: 'buf_vec' declared here
>> 1838 | struct buf_vector buf_vec[BUF_VECTOR_MAX];
>> | ^~~~~~~
>> cc1: all warnings being treated as errors
>>
>> Actually, there are eight places to see the same codes in the file
>> lib/vhost/virtio_net.c, and all these `buf_vec` arraies are
>> initialized by sub-function calls under various conditions.
>>
>> Although It's hard to understand why gcc just emits warning at one
>> of the eight places, adding validity checks for array length is
>> reasonable and can also fix the warning.
>>
>> Signed-off-by: David Marchand <david.marchand@redhat.com>
>> Signed-off-by: Min Zhou <zhoumin@loongson.cn>
>> ---
>> lib/vhost/virtio_net.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
> Just want you to know that your patch is still pending because by accident
> your fix is almost the same as a previous patch that fixes a real issue but
> that patch is still in progress:
>
> http://patchwork.dpdk.org/project/dpdk/patch/20220802004938.23670-2-cfontana@suse.de/
>
> Thanks,
> Chenbo
Thanks for your helpful reply.
I think I can drop this patch if the patch you mentioned above could be
accepted.
Thanks,
Min Zhou
>> diff --git a/lib/vhost/virtio_net.c b/lib/vhost/virtio_net.c
>> index 35fa4670fd..99233f1759 100644
>> --- a/lib/vhost/virtio_net.c
>> +++ b/lib/vhost/virtio_net.c
>> @@ -1153,7 +1153,7 @@ mbuf_to_desc(struct virtio_net *dev, struct
>> vhost_virtqueue *vq,
>> struct virtio_net_hdr_mrg_rxbuf tmp_hdr, *hdr = NULL;
>> struct vhost_async *async = vq->async;
>>
>> - if (unlikely(m == NULL))
>> + if (unlikely(m == NULL || nr_vec == 0))
>> return -1;
>>
>> buf_addr = buf_vec[vec_idx].buf_addr;
>> @@ -2673,6 +2673,9 @@ desc_to_mbuf(struct virtio_net *dev, struct
>> vhost_virtqueue *vq,
>> struct vhost_async *async = vq->async;
>> struct async_inflight_info *pkts_info;
>>
>> + if (unlikely(nr_vec == 0))
>> + return -1;
>> +
>> buf_addr = buf_vec[vec_idx].buf_addr;
>> buf_iova = buf_vec[vec_idx].buf_iova;
>> buf_len = buf_vec[vec_idx].buf_len;
>> --
>> 2.31.1
next prev parent reply other threads:[~2022-09-26 3:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 8:29 Min Zhou
2022-09-01 0:06 ` zhoumin
2022-09-09 9:07 ` zhoumin
2022-09-26 2:57 ` Xia, Chenbo
2022-09-26 3:25 ` zhoumin [this message]
2022-10-05 14:51 ` Maxime Coquelin
2022-10-06 3:56 ` zhoumin
2022-10-06 3:57 ` zhoumin
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=7352946c-b313-d5ea-e2a0-6f761997594d@loongson.cn \
--to=zhoumin@loongson.cn \
--cc=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maobibo@loongson.cn \
--cc=maxime.coquelin@redhat.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;
as well as URLs for NNTP newsgroup(s).