From: Thomas Monjalon <thomas@monjalon.net>
To: "Zhang, AlvinX" <alvinx.zhang@intel.com>
Cc: "Liang, Cunming" <cunming.liang@intel.com>,
dev@dpdk.org, "stable@dpdk.org" <stable@dpdk.org>,
"Guo, Jia" <jia.guo@intel.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] test: fix buffer overflow
Date: Tue, 19 Jan 2021 11:38:46 +0100 [thread overview]
Message-ID: <4572309.mWVYpkDgUe@thomas> (raw)
In-Reply-To: <75f952994d984b3e80d80d97c872492a@intel.com>
> > > From: Alvin Zhang <alvinx.zhang@intel.com>
> > >
> > > The Tx buffer may overflow when there is more than one port.
> > >
> > > Signed-off-by: Alvin Zhang <alvinx.zhang@intel.com>
> > >
> > > Fixes: 002ade70e933 ("app/test: measure cycles per packet in Rx/Tx")
> > > Cc: stable@dpdk.org
> Acked-by: Jeff Guo <jia.guo@intel.com>
Applied, thanks
prev parent reply other threads:[~2021-01-19 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 9:46 [dpdk-stable] " Zhang,Alvin
2020-11-26 9:30 ` [dpdk-stable] [dpdk-dev] " Ling, WeiX
2021-01-15 8:31 ` Guo, Jia
2021-01-15 8:59 ` Guo, Jia
2021-01-19 10:38 ` Thomas Monjalon [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=4572309.mWVYpkDgUe@thomas \
--to=thomas@monjalon.net \
--cc=alvinx.zhang@intel.com \
--cc=cunming.liang@intel.com \
--cc=dev@dpdk.org \
--cc=jia.guo@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).