From: Akhil Goyal <gakhil@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
Radu Nicolau <radu.nicolau@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Jerin Jacob <jerinj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v2] examples/ipsec-secgw: fix dequeue count from cryptodev
Date: Wed, 9 Oct 2024 14:55:53 +0000 [thread overview]
Message-ID: <CO6PR18MB4484B0AB120D13C9141BDDDDD87F2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB4484D810D46A80E1F8601B43D8622@CO6PR18MB4484.namprd18.prod.outlook.com>
> > Subject: [PATCH v2] examples/ipsec-secgw: fix dequeue count from cryptodev
> >
> > Setting dequeue packet count to max of MAX_PKT_BURST
> > size instead of MAX_PKTS.
> >
> > Dequeue from cryptodev is called with MAX_PKTS but
> > routing functions allocate hop/dst_ip arrays of
> > size MAX_PKT_BURST. This can corrupt stack causing
> > stack smashing error when more than MAX_PKT_BURST
> > packets are returned from cryptodev.
> >
> > Fixes: a2b445b810ac ("examples/ipsec-secgw: allow larger burst size for
> > vectors")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com>
> Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2024-10-09 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 6:58 [PATCH] " Tejasree Kondoj
2024-09-13 7:07 ` [PATCH v2] " Tejasree Kondoj
2024-09-18 5:44 ` Akhil Goyal
2024-10-09 14:55 ` Akhil Goyal [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=CO6PR18MB4484B0AB120D13C9141BDDDDD87F2@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=ktejasree@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=radu.nicolau@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).