From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: Ori Kam <orika@mellanox.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"viacheslavo@mellanox.com" <viacheslavo@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v4] app/testpmd: fix copying the name of the dynflag
Date: Tue, 4 Feb 2020 14:39:34 +0000 [thread overview]
Message-ID: <DM6PR11MB3914C3B1DFFB86298145A83CEF030@DM6PR11MB3914.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1580823586-144444-1-git-send-email-orika@mellanox.com>
> -----Original Message-----
> From: Ori Kam <orika@mellanox.com>
> Sent: Tuesday, February 4, 2020 1:40 PM
> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>; Iremonger, Bernard
> <bernard.iremonger@intel.com>
> Cc: dev@dpdk.org; orika@mellanox.com; Yigit, Ferruh
> <ferruh.yigit@intel.com>; viacheslavo@mellanox.com
> Subject: [PATCH v4] app/testpmd: fix copying the name of the dynflag
>
> When working with testpmd and setting the dynflag name, we copy the
> name given by the cmd to the dynflag name.
>
> The issue is that the size of the dynflag name is smaller then the string used
> by testpmd.
>
> This commit solves this issue by checking that the length of the requested
> flag name is not too long.
>
> Coverity issue: 353610
>
> Fixes: b57b66a97ebf ("app/testpmd: support mbuf dynamic flag")
>
> Signed-off-by: Ori Kam <orika@mellanox.com>
Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
next prev parent reply other threads:[~2020-02-04 14:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 13:22 [dpdk-dev] [PATCH] " Ori Kam
2020-01-30 16:54 ` Iremonger, Bernard
2020-01-30 18:55 ` Ori Kam
2020-01-30 19:09 ` Ori Kam
2020-01-30 20:55 ` [dpdk-dev] [PATCH v2] " Ori Kam
2020-01-30 21:04 ` [dpdk-dev] [PATCH v3] " Ori Kam
2020-01-31 14:02 ` Ferruh Yigit
2020-02-02 9:12 ` Ori Kam
2020-02-04 10:45 ` Iremonger, Bernard
2020-02-04 11:12 ` Ori Kam
2020-02-04 12:18 ` Iremonger, Bernard
2020-02-04 13:03 ` Ori Kam
2020-02-04 13:39 ` [dpdk-dev] [PATCH v4] " Ori Kam
2020-02-04 14:39 ` Iremonger, Bernard [this message]
2020-02-04 17:58 ` 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=DM6PR11MB3914C3B1DFFB86298145A83CEF030@DM6PR11MB3914.namprd11.prod.outlook.com \
--to=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jingjing.wu@intel.com \
--cc=orika@mellanox.com \
--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).