From: Ori Kam <orika@mellanox.com>
To: Wenzhuo Lu <wenzhuo.lu@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>
Cc: dev@dpdk.org, orika@mellanox.com, ferruh.yigit@intel.com,
viacheslavo@mellanox.com
Subject: [dpdk-dev] [PATCH v4] app/testpmd: fix copying the name of the dynflag
Date: Tue, 4 Feb 2020 13:39:46 +0000 [thread overview]
Message-ID: <1580823586-144444-1-git-send-email-orika@mellanox.com> (raw)
In-Reply-To: <1580390564-186435-1-git-send-email-orika@mellanox.com>
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>
---
V4:
* Address ML comments
V3:
* Fix style issue.
V2:
* change to check the requested flag name.
---
app/test-pmd/cmdline.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/app/test-pmd/cmdline.c b/app/test-pmd/cmdline.c
index dab22bc..45602cc 100644
--- a/app/test-pmd/cmdline.c
+++ b/app/test-pmd/cmdline.c
@@ -18867,14 +18867,18 @@ struct cmd_config_tx_dynf_specific_result {
return;
flag = rte_mbuf_dynflag_lookup(res->name, NULL);
if (flag <= 0) {
- strcpy(desc_flag.name, res->name);
+ if (strlcpy(desc_flag.name, res->name,
+ RTE_MBUF_DYN_NAMESIZE) >= RTE_MBUF_DYN_NAMESIZE) {
+ printf("Flag name too long\n");
+ return;
+ }
desc_flag.flags = 0;
flag = rte_mbuf_dynflag_register(&desc_flag);
if (flag < 0) {
printf("Can't register flag\n");
return;
}
- strcpy(dynf_names[flag], res->name);
+ strcpy(dynf_names[flag], desc_flag.name);
}
old_port_flags = ports[res->port_id].mbuf_dynf;
if (!strcmp(res->value, "set")) {
--
1.8.3.1
next prev parent reply other threads:[~2020-02-04 13:39 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 ` Ori Kam [this message]
2020-02-04 14:39 ` [dpdk-dev] [PATCH v4] " Iremonger, Bernard
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=1580823586-144444-1-git-send-email-orika@mellanox.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=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).