From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: jianfeng.tan@intel.com
Subject: [dpdk-dev] [PATCH] ipc: fix duplicate string copy
Date: Thu, 3 May 2018 11:35:26 +0100 [thread overview]
Message-ID: <e4d2b6acfa50621874bdb92c3c8db9f97156754e.1525343708.git.anatoly.burakov@intel.com> (raw)
Coverity issue: 272582
Fixes: 2147c0950580 ("ipc: clean up code")
Cc: jianfeng.tan@intel.com
Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
lib/librte_eal/common/eal_common_proc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/lib/librte_eal/common/eal_common_proc.c b/lib/librte_eal/common/eal_common_proc.c
index 611aba2..707d8ab 100644
--- a/lib/librte_eal/common/eal_common_proc.c
+++ b/lib/librte_eal/common/eal_common_proc.c
@@ -870,7 +870,6 @@ mp_request_async(const char *dst, struct rte_mp_msg *req,
pending_req->type = REQUEST_TYPE_ASYNC;
strlcpy(pending_req->dst, dst, sizeof(pending_req->dst));
- strcpy(pending_req->dst, dst);
pending_req->request = req;
pending_req->reply = reply_msg;
pending_req->async.param = param;
--
2.7.4
next reply other threads:[~2018-05-03 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 10:35 Anatoly Burakov [this message]
2018-05-09 13:58 ` Van Haaren, Harry
2018-05-14 1:21 ` Thomas Monjalon
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=e4d2b6acfa50621874bdb92c3c8db9f97156754e.1525343708.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@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).