From: Thomas Monjalon <thomas@monjalon.net>
To: Rahul Bhansali <rbhansali@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
Conor Walsh <conor.walsh@intel.com>
Subject: Re: [EXT] Re: [PATCH] examples/l3fwd: resolve stack buffer overflow issue
Date: Wed, 09 Mar 2022 20:07:02 +0100 [thread overview]
Message-ID: <8029134.GJh79HuArf@thomas> (raw)
In-Reply-To: <CO6PR18MB3844B0B47EFA841F04E2CA62B80A9@CO6PR18MB3844.namprd18.prod.outlook.com>
09/03/2022 16:24, Rahul Bhansali:
> Hi Thomas,
>
> From: Thomas Monjalon <thomas@monjalon.net>
> > 11/01/2022 13:50, Rahul Bhansali:
> > > /* copy rest of the packets into the TX buffer. */
> > > len = num - n;
> > > + if (len == 0)
> > > + goto exit;
> > > +
> >
> > I don't understand how it can fix something.
> > There is already "while (j < len)" with j and len being 0, the loop should not be
> > effective in this case.
>
> This Switch will execute Case statement first even before considering the while condition or anything else before case statement. While condition will be executed only after all switch cases are executed.
I don't know this construct. Is it part of the C standard?
We learn something everyday :)
> Hence in case of len = 0 and n > 28, it is throwing stack buffer overflow error.
>
> Below is sample code to simulate the while loop behavior inside switch. Checked it for both x86 and arm64.
> https://godbolt.org/z/4Kecqbsde
>
> >
> > > j = 0;
> > > switch (len % FWDSTEP) {
> > > while (j < len) {
next prev parent reply other threads:[~2022-03-09 19:07 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 [this message]
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=8029134.GJh79HuArf@thomas \
--to=thomas@monjalon.net \
--cc=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).