From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ye Xiaolong <xiaolong.ye@intel.com>
Cc: dev@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>,
Tiwei Bie <tiwei.bie@intel.com>,
Zhihong Wang <zhihong.wang@intel.com>,
xiao.w.wang@intel.com, Rami Rosen <roszenrami@gmail.com>,
Wang Haiyue <haiyue.wang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v8 2/2] examples/vdpa: introduce a new sample for vDPA
Date: Wed, 3 Oct 2018 08:48:12 +0100 [thread overview]
Message-ID: <621e5389-64c3-0311-3baf-45d5112430f6@intel.com> (raw)
In-Reply-To: <20181003060420.GC78385@intel.com>
On 10/3/2018 7:04 AM, Ye Xiaolong wrote:
> Hi, Ferruh,
>
> On 10/02, Ferruh Yigit wrote:
>> On 9/28/2018 10:47 PM, Xiaolong Ye wrote:
>>> The vdpa sample application creates vhost-user sockets by using the
>>> vDPA backend. vDPA stands for vhost Data Path Acceleration which utilizes
>>> virtio ring compatible devices to serve virtio driver directly to enable
>>> datapath acceleration. As vDPA driver can help to set up vhost datapath,
>>> this application doesn't need to launch dedicated worker threads for vhost
>>> enqueue/dequeue operations.
>>>
>>> Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com>
>>> Acked-by: Xiao Wang <xiao.w.wang@intel.com>
>>> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>>
>> <...>
>>
>>> +static int
>>> +parse_args(int argc, char **argv)
>>> +{
>>> + static const char *short_option = "i";
>>> + static struct option long_option[] = {
>>> + {"iface", required_argument, NULL, 0},
>>> + {"interactive", no_argument, &interactive, 1},
>>> + {"client", no_argument, &client_mode, 1},
>>> + {NULL, 0, 0, 0},
>>> + };
>>> + int opt, idx;
>>> + char *prgname = argv[0];
>>> +
>>> + while ((opt = getopt_long(argc, argv, short_option, long_option, &idx))
>>> + != EOF) {
>>> + switch (opt) {
>>> + case 'i':
>>> + printf("Interactive-mode selected\n");
>>> + interactive = 1;
>>> + break;
>>> + /* long options */
>>> + case 0:
>>> + if (strncmp(long_option[idx].name, "iface",
>>> + MAX_PATH_LEN) == 0) {
>>> + strncpy(iface, optarg, MAX_PATH_LEN);
>>
>> Giving compiler warning [1], rte_strscpy() is safer to use.
>>
>> [1]
>> In function ‘parse_args’,
>>
>>
>>
>> inlined from ‘main’ at .../examples/vdpa/main.c:419:8:
>>
>>
>>
>> .../examples/vdpa/main.c:76:5: error: ‘strncpy’ specified bound 128 equals
>> destination size [-Werror=stringop-truncation]
>>
>>
>> strncpy(iface, optarg, MAX_PATH_LEN);
>>
>>
>>
>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Thanks for the finding, by the way, how do you get this warning? I can't see
> it in my local build, what compiler you used?
gcc,
$ gcc --version
gcc (GCC) 8.1.1 20180712 (Red Hat 8.1.1-5)
next prev parent reply other threads:[~2018-10-03 7:48 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 22:28 [dpdk-dev] [PATCH v3 0/2] introduce vdpa sample Xiaolong Ye
2018-09-20 22:28 ` [dpdk-dev] [PATCH v3 1/2] vhost: introduce API to get vDPA device number Xiaolong Ye
2018-09-20 22:28 ` [dpdk-dev] [PATCH v3 2/2] examples/vdpa: introduce a new sample for vDPA Xiaolong Ye
2018-09-21 5:07 ` Wang, Xiao W
2018-09-22 11:04 ` Ye Xiaolong
2018-09-24 8:42 ` [dpdk-dev] [PATCH v4 0/2] introduce vdpa sample Xiaolong Ye
2018-09-24 8:42 ` [dpdk-dev] [PATCH v4 1/2] vhost: introduce API to get vDPA device number Xiaolong Ye
2018-09-24 8:42 ` [dpdk-dev] [PATCH v4 2/2] examples/vdpa: introduce a new sample for vDPA Xiaolong Ye
2018-09-24 4:12 ` Wang, Xiao W
2018-09-24 21:30 ` Ye Xiaolong
2018-09-25 12:07 ` [dpdk-dev] [PATCH v5 0/2] introduce vdpa sample Xiaolong Ye
2018-09-25 12:07 ` [dpdk-dev] [PATCH v5 1/2] vhost: introduce API to get vDPA device number Xiaolong Ye
2018-09-25 12:07 ` [dpdk-dev] [PATCH v5 2/2] examples/vdpa: introduce a new sample for vDPA Xiaolong Ye
2018-09-25 8:32 ` Wang, Xiao W
2018-09-26 9:06 ` [dpdk-dev] [PATCH v6 0/2] introduce vdpa sample Xiaolong Ye
2018-09-26 3:15 ` Wang, Xiao W
2018-09-26 9:06 ` [dpdk-dev] [PATCH v6 1/2] vhost: introduce API to get vDPA device number Xiaolong Ye
2018-09-26 9:06 ` [dpdk-dev] [PATCH v6 2/2] examples/vdpa: introduce a new sample for vDPA Xiaolong Ye
2018-09-27 16:37 ` Maxime Coquelin
2018-09-28 7:32 ` Ye Xiaolong
2018-09-28 11:23 ` [dpdk-dev] [PATCH v7 0/2] introduce vdpa sample Xiaolong Ye
2018-09-28 11:23 ` [dpdk-dev] [PATCH v7 1/2] vhost: introduce API to get vDPA device number Xiaolong Ye
2018-09-28 11:23 ` [dpdk-dev] [PATCH v7 2/2] examples/vdpa: introduce a new sample for vDPA Xiaolong Ye
2018-09-28 7:31 ` Maxime Coquelin
2018-09-28 14:33 ` Ye Xiaolong
2018-09-28 7:49 ` Maxime Coquelin
2018-09-28 15:17 ` Ye Xiaolong
2018-09-28 8:31 ` Maxime Coquelin
2018-09-28 17:37 ` Ye Xiaolong
2018-09-28 21:47 ` [dpdk-dev] [PATCH v8 0/2] introduce vdpa sample Xiaolong Ye
2018-09-28 21:47 ` [dpdk-dev] [PATCH v8 1/2] vhost: introduce API to get vDPA device number Xiaolong Ye
2018-10-02 13:19 ` Ferruh Yigit
2018-10-03 5:53 ` Ye Xiaolong
2018-09-28 21:47 ` [dpdk-dev] [PATCH v8 2/2] examples/vdpa: introduce a new sample for vDPA Xiaolong Ye
2018-10-02 14:03 ` Ferruh Yigit
2018-10-03 6:04 ` Ye Xiaolong
2018-10-03 7:48 ` Ferruh Yigit [this message]
2019-01-17 14:37 ` Shahaf Shuler
2019-01-17 15:13 ` Ye Xiaolong
2019-01-17 15:17 ` Shahaf Shuler
2018-10-02 12:51 ` [dpdk-dev] [PATCH v8 0/2] introduce vdpa sample Maxime Coquelin
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=621e5389-64c3-0311-3baf-45d5112430f6@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=roszenrami@gmail.com \
--cc=tiwei.bie@intel.com \
--cc=xiao.w.wang@intel.com \
--cc=xiaolong.ye@intel.com \
--cc=zhihong.wang@intel.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).