From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Eli Britstein <elibr@nvidia.com>
Cc: stable@dpdk.org, Matan Azrad <matan@nvidia.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [PATCH 19.11] app/testpmd: fix packet burst spreading stats
Date: Wed, 1 Dec 2021 11:31:29 +0100 [thread overview]
Message-ID: <CAATJJ0+h69NXwGs2havnfF0eY5SDEHMfPXP+JQwOVw=Xh4vJHw@mail.gmail.com> (raw)
In-Reply-To: <20211201072520.11808-1-elibr@nvidia.com>
On Wed, Dec 1, 2021 at 8:26 AM Eli Britstein <elibr@nvidia.com> wrote:
>
> [ upstream commit 6a8b64fd5e9e8f5572ea4d9de40a1cff23498246 ]
>
Thanks, applied
> RX/TX functions (rte_eth_rx_burst/rte_eth_tx_burst) get 'nb_pkts'
> argument, which specifies the maximum number to receive/transmit.
> It can be 0..nb_pkts, meaning nb_pkts+1 options.
> Testpmd can provide statistics of the burst sizes ('set
> record-burst-stats on') by incrementing an array cell of index
> <burst-size>. This array is mistakenly [MAX_PKT_BURST] size. Receiving
> the maximum burst will cause out of bound write.
> Enlarge the spread stats array by one cell to fix it.
>
> Fixes: af75078fece3 ("first public release")
>
> Signed-off-by: Eli Britstein <elibr@nvidia.com>
> Reviewed-by: Matan Azrad <matan@nvidia.com>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> app/test-pmd/testpmd.c | 2 +-
> app/test-pmd/testpmd.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/app/test-pmd/testpmd.c b/app/test-pmd/testpmd.c
> index bd15fe9e53..f4a54102ca 100644
> --- a/app/test-pmd/testpmd.c
> +++ b/app/test-pmd/testpmd.c
> @@ -1605,7 +1605,7 @@ pkt_burst_stats_display(const char *rx_tx, struct pkt_burst_stats *pbs)
> total_burst = 0;
> burst_stats[0] = burst_stats[1] = burst_stats[2] = 0;
> pktnb_stats[0] = pktnb_stats[1] = pktnb_stats[2] = 0;
> - for (nb_pkt = 0; nb_pkt < MAX_PKT_BURST; nb_pkt++) {
> + for (nb_pkt = 0; nb_pkt < MAX_PKT_BURST + 1; nb_pkt++) {
> nb_burst = pbs->pkt_burst_spread[nb_pkt];
> if (nb_burst == 0)
> continue;
> diff --git a/app/test-pmd/testpmd.h b/app/test-pmd/testpmd.h
> index bbe18a7191..334bcc28e6 100644
> --- a/app/test-pmd/testpmd.h
> +++ b/app/test-pmd/testpmd.h
> @@ -86,7 +86,7 @@ enum {
> * that are recorded for each forwarding stream.
> */
> struct pkt_burst_stats {
> - unsigned int pkt_burst_spread[MAX_PKT_BURST];
> + unsigned int pkt_burst_spread[MAX_PKT_BURST + 1];
> };
> #endif
>
> --
> 2.28.0.2311.g225365fb51
>
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
prev parent reply other threads:[~2021-12-01 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 7:25 Eli Britstein
2021-12-01 10:31 ` Christian Ehrhardt [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='CAATJJ0+h69NXwGs2havnfF0eY5SDEHMfPXP+JQwOVw=Xh4vJHw@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=elibr@nvidia.com \
--cc=ferruh.yigit@intel.com \
--cc=matan@nvidia.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).