DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Anoob Joseph <anoobj@marvell.com>,
	Volodymyr Fialko <vfialko@marvell.com>,
	 "dev@dpdk.org" <dev@dpdk.org>,
	Radu Nicolau <radu.nicolau@intel.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Volodymyr Fialko <vfialko@marvell.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXT] [PATCH] examples/ipsec-secgw: fix uninitialized memory access
Date: Wed, 11 May 2022 19:41:03 +0000	[thread overview]
Message-ID: <CO6PR18MB4484E31A5EB2BF2AE7AA92E4D8C89@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB4484288D5FE2F1BBD9857301D8C89@CO6PR18MB4484.namprd18.prod.outlook.com>



> -----Original Message-----
> From: Akhil Goyal
> Sent: Thursday, May 12, 2022 1:06 AM
> To: Anoob Joseph <anoobj@marvell.com>; Volodymyr Fialko
> <vfialko@marvell.com>; dev@dpdk.org; Radu Nicolau
> <radu.nicolau@intel.com>
> Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Volodymyr Fialko
> <vfialko@marvell.com>
> Subject: RE: [EXT] [PATCH] examples/ipsec-secgw: fix uninitialized memory
> access
> 
> 
> > > rte_flow_validate and rte_flow_create not always initialize flow error.
> > > Using error.message in some error cases will cause read from uninitialized
> > > memory.
> > >
> > > Fixes: 6738c0a9569 ("examples/ipsec-secgw: support flow director")
> > >
> > > Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
> > > ---
> > >  examples/ipsec-secgw/flow.c  | 2 +-
> > >  examples/ipsec-secgw/ipsec.c | 2 +-
> > >  2 files changed, 2 insertions(+), 2 deletions(-)
> > >
> >
> > Acked-by: Anoob Joseph <anoobj@marvell.com>
> 
> Acked-by: Akhil Goyal <gakhil@marvell.com>
> 
> Applied to dpdk-next-crypto
> 
> Thanks.

Cc: stable@dpdk.org

      reply	other threads:[~2022-05-11 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 11:29 Volodymyr Fialko
2022-04-28  4:42 ` [EXT] " Anoob Joseph
2022-05-11 19:36   ` Akhil Goyal
2022-05-11 19:41     ` 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=CO6PR18MB4484E31A5EB2BF2AE7AA92E4D8C89@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=radu.nicolau@intel.com \
    --cc=stable@dpdk.org \
    --cc=vfialko@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).