From: Thomas Monjalon <thomas@monjalon.net>
To: Rahul Bhansali <rbhansali@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Walsh, Conor" <conor.walsh@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [PATCH] examples/l3fwd: resolve stack buffer overflow issue
Date: Mon, 14 Mar 2022 23:16:20 +0100 [thread overview]
Message-ID: <2548073.k3LOHGUjKi@thomas> (raw)
In-Reply-To: <DM6PR11MB44919F79078CFD10383C746F9A0A9@DM6PR11MB4491.namprd11.prod.outlook.com>
> > This patch fixes the stack buffer overflow error reported
> > from AddressSanitizer.
> > Function send_packetsx4() tries to access out of bound data
> > from rte_mbuf and fill it into TX buffer even in the case
> > where no pending packets (len = 0).
> > Performance impact:- No
> >
> > ASAN error report:-
> > ==819==ERROR: AddressSanitizer: stack-buffer-overflow on address
> > 0xffffe2c0dcf0 at pc 0x0000005e791c bp 0xffffe2c0d7e0 sp 0xffffe2c0d800
> > READ of size 8 at 0xffffe2c0dcf0 thread T0
> > #0 0x5e7918 in send_packetsx4 ../examples/l3fwd/l3fwd_common.h:251
> > #1 0x5e7918 in send_packets_multi ../examples/l3fwd/l3fwd_neon.h:226
> >
> > Signed-off-by: Rahul Bhansali <rbhansali@marvell.com>
> Reviewed-by: Conor Walsh <conor.walsh@intel.com>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Applied, thanks.
prev parent reply other threads:[~2022-03-14 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 12:50 Rahul Bhansali
2022-03-07 4:27 ` Rahul Bhansali
2022-03-07 6:45 ` Rahul Bhansali
2022-03-07 10:46 ` Walsh, Conor
2022-03-08 11:20 ` Thomas Monjalon
2022-03-09 15:24 ` [EXT] " Rahul Bhansali
2022-03-09 19:07 ` Thomas Monjalon
2022-03-10 9:38 ` Rahul Bhansali
2022-03-09 15:57 ` Ananyev, Konstantin
2022-03-14 22:16 ` 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=2548073.k3LOHGUjKi@thomas \
--to=thomas@monjalon.net \
--cc=conor.walsh@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=rbhansali@marvell.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).