From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ori Kam <orika@mellanox.com>, Wenzhuo Lu <wenzhuo.lu@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Slava Ovsiienko <viacheslavo@mellanox.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] app/testpmd: fix uninitialized members of mpls
Date: Mon, 3 Feb 2020 17:46:24 +0000 [thread overview]
Message-ID: <7f2f8546-00e0-1e16-652f-ff2f030f7ab6@intel.com> (raw)
In-Reply-To: <0439a4bb-1260-90f9-a678-13e3237345f6@intel.com>
On 2/3/2020 10:21 AM, Ferruh Yigit wrote:
> On 2/2/2020 8:23 AM, Ori Kam wrote:
>> Hi Ferruh,
>>
>> PSB,
>> Thanks,
>> Ori
>>
>>> -----Original Message-----
>>> From: Ferruh Yigit <ferruh.yigit@intel.com>
>>> Sent: Friday, January 31, 2020 1:08 PM
>>> To: Ori Kam <orika@mellanox.com>; Wenzhuo Lu <wenzhuo.lu@intel.com>;
>>> Jingjing Wu <jingjing.wu@intel.com>; Bernard Iremonger
>>> <bernard.iremonger@intel.com>
>>> Cc: dev@dpdk.org; Slava Ovsiienko <viacheslavo@mellanox.com>;
>>> stable@dpdk.org
>>> Subject: Re: [PATCH] app/testpmd: fix uninitialized members of mpls
>>>
>>> On 1/30/2020 4:59 PM, Ori Kam wrote:
>>>> Some of the memebers of the mpls struct are not initialized.
>>>> this commit init the uninitialized members.
>>>>
>>>> Coverity issue: 325735
>>>> Fixes: 3e77031be855 ("app/testpmd: add MPLSoGRE encapsulation")
>>>> Cc: stable@dpdk.org
>>>>
>>>> Signed-off-by: Ori Kam <orika@mellanox.com>
>>>> ---
>>>> app/test-pmd/cmdline_flow.c | 4 +++-
>>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/app/test-pmd/cmdline_flow.c b/app/test-pmd/cmdline_flow.c
>>>> index e99e24c..c2cc4c5 100644
>>>> --- a/app/test-pmd/cmdline_flow.c
>>>> +++ b/app/test-pmd/cmdline_flow.c
>>>> @@ -4576,7 +4576,9 @@ static int comp_set_raw_index(struct context *,
>>> const struct token *,
>>>> struct rte_flow_item_gre gre = {
>>>> .protocol = rte_cpu_to_be_16(ETHER_TYPE_MPLS_UNICAST),
>>>> };
>>>> - struct rte_flow_item_mpls mpls;
>>>> + struct rte_flow_item_mpls mpls = {
>>>> + .ttl = 0,
>>>> + };
>>>
>>> why not use "= {0};", the end result will be same, struct will be all zeroed out
>>> in both case, "= {0};" makes the intention more obvious I think.
>>>
>>
>> On some compilers this kind of initialization result in an error:
>> error: missing braces around initializer
>
> As far as I remember, that is triggered with old compiler, when you are
> initializing array of structs, or first element of the struct is an array (which
> is the case for mpls struct), in that case ={{0}} was solving the issue.
>
> Anyway, I got the concern, the patch looks good to me.
Also seems "={}" is working in that case, thanks to Stephen, it is cleaner than
"={{0}}", what do you think about using "={}" ?
>
>> it looks like a known issue of GCC
>> So I just prefer to init the relevant fields.
>>
>>>> uint8_t *header;
>>>> int ret;
>>>>
>>>>
>>
>
next prev parent reply other threads:[~2020-02-03 17:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 16:59 [dpdk-dev] " Ori Kam
2020-01-31 11:07 ` Ferruh Yigit
2020-02-02 8:23 ` Ori Kam
2020-02-03 10:21 ` Ferruh Yigit
2020-02-03 17:46 ` Ferruh Yigit [this message]
2020-02-04 7:50 ` [dpdk-dev] [dpdk-stable] " Ori Kam
2020-02-04 11:49 ` [dpdk-dev] " Ferruh Yigit
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=7f2f8546-00e0-1e16-652f-ff2f030f7ab6@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=orika@mellanox.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@mellanox.com \
--cc=wenzhuo.lu@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).