From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Pattan, Reshma" <reshma.pattan@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Singh, Jasvinder" <jasvinder.singh@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/softnic: fix string copy
Date: Fri, 2 Nov 2018 11:47:45 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E7F1F9D@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1540981019-26174-1-git-send-email-reshma.pattan@intel.com>
> -----Original Message-----
> From: Pattan, Reshma
> Sent: Wednesday, October 31, 2018 10:17 AM
> To: dev@dpdk.org
> Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Singh, Jasvinder
> <jasvinder.singh@intel.com>; Pattan, Reshma <reshma.pattan@intel.com>
> Subject: [PATCH v2] net/softnic: fix string copy
>
> Use strlcpy instead of strcpy to avoid buffer overrun.
>
> Coverity issues: 323475,323478,323514,323515
>
> Fixes: b767f8efc8 ("net/softnic: replace pointers with arrays")
> Fixes: c169b6a588 ("net/softnic: map flow attribute to pipeline table")
> CC: cristian.dumitrescu@intel.com
> CC: jasvinder.singh@intel.com
>
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
> ---
> v2: merge the below patches into single patch.
>
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Applied to next-pipeline tree, thanks!
prev parent reply other threads:[~2018-11-02 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 14:22 [dpdk-dev] [PATCH 1/4] " Reshma Pattan
2018-10-30 14:22 ` [dpdk-dev] [PATCH 2/4] " Reshma Pattan
2018-10-30 14:22 ` [dpdk-dev] [PATCH 3/4] " Reshma Pattan
2018-10-30 14:22 ` [dpdk-dev] [PATCH 4/4] " Reshma Pattan
2018-10-31 9:47 ` [dpdk-dev] [PATCH 1/4] " Thomas Monjalon
2018-10-31 10:16 ` [dpdk-dev] [PATCH v2] " Reshma Pattan
2018-11-02 11:47 ` Dumitrescu, Cristian [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=3EB4FA525960D640B5BDFFD6A3D891268E7F1F9D@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=reshma.pattan@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).