patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Lavanya Govindarajan <lavanyax.govindarajan@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "reshma.pattan@intel.com" <reshma.pattan@intel.com>,
	"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] app/test-compress-perf: fix out-of-bounds read
Date: Fri, 27 Sep 2019 14:15:26 +0000	[thread overview]
Message-ID: <VE1PR04MB6639450C754D4C864E3AF4B1E6810@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1569504605-1344-1-git-send-email-lavanyax.govindarajan@intel.com>


> One issue caught by Coverity 344984
> *overrun-local: Overrunning array cperf_test_type_strs of 2 8-byte elements
> 
> The array cperf_test_type_strs defined in app/test-compress-perf conflicts
> with the same name being defined in app/test-crypto-perf. Due to which
> coverity reports error.
> 
> The fix is to rename "cperf_test_type_strs" into "comp_perf_test_type_strs"
> in app/test-compress-perf to avoid name confusion.
> 
> Coverity issue: 344984
> Fixes: 424dd6c8c1 ("app/compress-perf: add weak functions for multicore test")
> Fixes: 1a9b0f3504 ("app/compress-perf: add --ptest option")
> Fixes: 424dd6c8c1 ("app/compress-perf: add weak functions for multicore test")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Lavanya Govindarajan <lavanyax.govindarajan@intel.com>
> ---
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

Applied to dpdk-next-crypto

Thanks.

      reply	other threads:[~2019-09-27 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 13:30 [dpdk-stable] " Lavanya Govindarajan
2019-09-27 14:15 ` Akhil Goyal [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=VE1PR04MB6639450C754D4C864E3AF4B1E6810@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=lavanyax.govindarajan@intel.com \
    --cc=reshma.pattan@intel.com \
    --cc=stable@dpdk.org \
    /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).