From: Akhil Goyal <akhil.goyal@nxp.com>
To: Chaitanya Babu Talluri <tallurix.chaitanya.babu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "reshma.pattan@intel.com" <reshma.pattan@intel.com>,
"jananeex.m.parthasarathy@intel.com"
<jananeex.m.parthasarathy@intel.com>,
"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] app/test: fix possible overflow using strlcat
Date: Fri, 22 Mar 2019 14:31:06 +0000 [thread overview]
Message-ID: <27471792-68e7-497f-e5ec-38150c22e790@nxp.com> (raw)
Message-ID: <20190322143106.HQnjeBP4gLf-_EgtMx0ctk885KJr22bxy9RmKV3E30A@z> (raw)
In-Reply-To: <1552912596-2776-1-git-send-email-tallurix.chaitanya.babu@intel.com>
On 3/18/2019 6:06 PM, Chaitanya Babu Talluri wrote:
> strcat does not check the destination length and there might be
> chances of string overflow so instead of strcat, strlcat is used.
>
> Fixes: 6f4eec2565 ("test/crypto: enhance scheduler unit tests")
> Cc: stable@dpdk.org
>
> Signed-off-by: Chaitanya Babu Talluri <tallurix.chaitanya.babu@intel.com>
> ---
> v2: Updated title.
> ---
> app/test/test_cryptodev.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
next prev parent reply other threads:[~2019-03-22 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 13:14 [dpdk-dev] [PATCH] app/test: fix possible overflow with strcat Chaitanya Babu Talluri
2019-03-14 13:14 ` Chaitanya Babu Talluri
2019-03-18 12:36 ` [dpdk-dev] [PATCH v2] app/test: fix possible overflow using strlcat Chaitanya Babu Talluri
2019-03-18 12:36 ` Chaitanya Babu Talluri
2019-03-22 14:31 ` Akhil Goyal [this message]
2019-03-22 14:31 ` Akhil Goyal
2019-03-22 15:07 ` Akhil Goyal
2019-03-22 15:07 ` Akhil Goyal
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=27471792-68e7-497f-e5ec-38150c22e790@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=jananeex.m.parthasarathy@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=reshma.pattan@intel.com \
--cc=stable@dpdk.org \
--cc=tallurix.chaitanya.babu@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).