From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "Troy, Rebecca" <rebecca.troy@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
"Trybula, ArturX" <arturx.trybula@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Ashish Gupta <ashish.gupta@marvell.com>
Subject: Re: [dpdk-stable] [PATCH] test/compress: fix buffer overflow bug
Date: Mon, 20 Sep 2021 13:16:28 +0000 [thread overview]
Message-ID: <BL0PR11MB3043A2911216792FDAFDF142B8A09@BL0PR11MB3043.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210917151207.2315536-1-rebecca.troy@intel.com>
> -----Original Message-----
> From: Troy, Rebecca <rebecca.troy@intel.com>
> Sent: Friday, September 17, 2021 4:12 PM
> To: dev@dpdk.org
> Cc: Zhang, Roy Fan <roy.fan.zhang@intel.com>; Troy, Rebecca
> <rebecca.troy@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>; Trybula,
> ArturX <arturx.trybula@intel.com>; stable@dpdk.org; Ashish Gupta
> <ashish.gupta@marvell.com>
> Subject: [PATCH] test/compress: fix buffer overflow bug
>
> Fixes stack buffer overflow bug in compressdev autotest, which
> was caused by the use of buf_idx in the debug logs. Originally, buf_idx
> was treated as an array instead of the reference of an integar.
> This was fixed by replacing the use of buf_idx[priv_data->orig_idx] with
> the variable i.
>
> Fixes: 466a2c4bb5f4 ("test/compress: improve debug logs")
> Fixes: 6bbc5a923625 ("test/compress: refactor unit tests")
>
> Cc: fiona.trahe@intel.com
> Cc: arturx.trybula@intel.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Rebecca Troy <rebecca.troy@intel.com>
> ---
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2021-09-20 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 15:12 Rebecca Troy
2021-09-20 13:16 ` Zhang, Roy Fan [this message]
2021-09-24 17:54 ` 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=BL0PR11MB3043A2911216792FDAFDF142B8A09@BL0PR11MB3043.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=arturx.trybula@intel.com \
--cc=ashish.gupta@marvell.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=rebecca.troy@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).