From: "Walsh, Conor" <conor.walsh@intel.com>
To: Rahul Bhansali <rbhansali@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: RE: [PATCH] examples/l3fwd: resolve stack buffer overflow issue
Date: Mon, 7 Mar 2022 10:46:21 +0000 [thread overview]
Message-ID: <PH0PR11MB52071BC546A5314B7D49CD0BFF089@PH0PR11MB5207.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB3844961A16AB8530C41E0CA6B8089@CO6PR18MB3844.namprd18.prod.outlook.com>
Hi Rahul,
I must have forgot to put my tag on this because I thought I reviewed it already.
I reviewed and tested it again this morning.
Thanks,
Reviewed-by: Conor Walsh <conor.walsh@intel.com>
> -----Original Message-----
> From: Rahul Bhansali <rbhansali@marvell.com>
> Sent: Monday 7 March 2022 06:45
> To: Rahul Bhansali <rbhansali@marvell.com>; dev@dpdk.org; Walsh, Conor
> <conor.walsh@intel.com>; david.marchand@redhat.com
> Subject: RE: [PATCH] examples/l3fwd: resolve stack buffer overflow issue
>
> Ping..
>
> -----Original Message-----
> From: Rahul Bhansali <rbhansali@marvell.com>
> Sent: Tuesday, January 11, 2022 6:20 PM
> To: dev@dpdk.org; conor.walsh@intel.com; david.marchand@redhat.com
> Cc: Rahul Bhansali <rbhansali@marvell.com>
> Subject: [PATCH] examples/l3fwd: resolve stack buffer overflow issue
>
> 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>
> ---
> examples/l3fwd/l3fwd_common.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/examples/l3fwd/l3fwd_common.h
> b/examples/l3fwd/l3fwd_common.h index 7d83ff641a..de77711f88 100644
> --- a/examples/l3fwd/l3fwd_common.h
> +++ b/examples/l3fwd/l3fwd_common.h
> @@ -236,6 +236,9 @@ send_packetsx4(struct lcore_conf *qconf, uint16_t
> port, struct rte_mbuf *m[],
>
> /* copy rest of the packets into the TX buffer. */
> len = num - n;
> + if (len == 0)
> + goto exit;
> +
> j = 0;
> switch (len % FWDSTEP) {
> while (j < len) {
> @@ -258,6 +261,7 @@ send_packetsx4(struct lcore_conf *qconf, uint16_t
> port, struct rte_mbuf *m[],
> }
> }
>
> +exit:
> qconf->tx_mbufs[port].len = len;
> }
>
> --
> 2.25.1
next prev parent reply other threads:[~2022-03-07 10:46 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 [this message]
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
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=PH0PR11MB52071BC546A5314B7D49CD0BFF089@PH0PR11MB5207.namprd11.prod.outlook.com \
--to=conor.walsh@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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).