patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Dooley, Brian" <brian.dooley@intel.com>,
	Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Anoob Joseph <anoobj@marvell.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] examples/fips_validation: fix coverity issues
Date: Tue, 2 Jul 2024 15:44:12 +0000	[thread overview]
Message-ID: <CO6PR18MB448497966372C5B76C592BCAD8DC2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR11MB5056E12BA2AEF4B21CD1978083C82@SJ0PR11MB5056.namprd11.prod.outlook.com>

> Hey Gowrishankar,
> 
> > -----Original Message-----
> > From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> > Sent: Saturday, June 15, 2024 12:31 PM
> > To: dev@dpdk.org; Dooley, Brian <brian.dooley@intel.com>; Gowrishankar
> > Muthukrishnan <gmuthukrishn@marvell.com>
> > Cc: Anoob Joseph <anoobj@marvell.com>; stable@dpdk.org
> > Subject: [PATCH] examples/fips_validation: fix coverity issues
> >
> > Fix NULL dereference, out-of-bound, bad bit shift issues reported by coverity
> > scan.
> >
> > Coverity issue: 384440, 384435, 384433, 384429
> > Fixes: 36128a67c27 ("examples/fips_validation: add asymmetric validation")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> 
> Acked-by: Brian Dooley <brian.dooley@intel.com>
Applied to dpdk-next-crypto
Title updated as "examples/fips_validation: fix null dereference and out-of-bound"

Thanks.

      reply	other threads:[~2024-07-02 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-15 11:31 Gowrishankar Muthukrishnan
2024-06-17 17:49 ` Patrick Robb
2024-06-20 16:33 ` Dooley, Brian
2024-07-02 15:44   ` 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=CO6PR18MB448497966372C5B76C592BCAD8DC2@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=brian.dooley@intel.com \
    --cc=dev@dpdk.org \
    --cc=gmuthukrishn@marvell.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).