patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ori Kam <orika@mellanox.com>
To: Ferruh Yigit <ferruh.yigit@intel.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-stable] [PATCH] testpmd: fix init mpls struct
Date: Sun, 2 Feb 2020 08:05:59 +0000	[thread overview]
Message-ID: <AM6PR05MB51762FBCF32932BF9A7E1116DB010@AM6PR05MB5176.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <66360294-835a-92c3-6cb8-529f908d4c5c@intel.com>

Hi Ferruh,

> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Friday, January 31, 2020 1:01 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] testpmd: fix init mpls struct
> 
> On 1/30/2020 4:18 PM, Ori Kam wrote:
> > When adding mpls item we copy the structure, in some cases
> > the item is not initialized.
> >
> > This commit solves this by initializing the struct.
> >
> > Coverity issue: 325734
> > Fixes: a1191d39cb57 ("app/testpmd: add MPLSoUDP 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..42d90f5 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
> 
> I wasn't aware that this is valid 'c' syntax, no ',' at the end.
> 
> Anyway, I guess this patch has been superseded by following, right?
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatches.d
> pdk.org%2Fpatch%2F65383%2F&amp;data=02%7C01%7Corika%40mellanox.co
> m%7C413906e79d3942d283f108d7a63ce6d7%7Ca652971c7d2e4d9ba6a4d149
> 256f461b%7C0%7C0%7C637160652819605813&amp;sdata=MxJo%2BJ2t4TlvT%
> 2BM0SzkPzAX9m8IJUtGIfUiVa3AzXaY%3D&amp;reserved=0
> "app/testpmd: fix uninitialized members of mpls"
> 

Yes you are correct.
Sorry for incorrect versions,
I will send the relevant patch with version 2.

> > +	};
> >  	uint8_t *header;
> >  	int ret;
> >
> >


      reply	other threads:[~2020-02-02  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30 16:18 Ori Kam
2020-01-31 11:01 ` Ferruh Yigit
2020-02-02  8:05   ` Ori Kam [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=AM6PR05MB51762FBCF32932BF9A7E1116DB010@AM6PR05MB5176.eurprd05.prod.outlook.com \
    --to=orika@mellanox.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jingjing.wu@intel.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).