From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH] ipsec: fix use of uninitialized variable
Date: Wed, 19 Feb 2020 15:27:35 +0000 [thread overview]
Message-ID: <MWHPR1101MB21581AC3A635DB6AAD630661FC100@MWHPR1101MB2158.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM6PR11MB39145CF27CE6B4C7341245D9EF100@DM6PR11MB3914.namprd11.prod.outlook.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Iremonger, Bernard
> Sent: Wednesday, February 19, 2020 2:15 PM
> To: Ananyev, Konstantin <konstantin.ananyev@intel.com>; dev@dpdk.org
> Cc: akhil.goyal@nxp.com; Ananyev, Konstantin
> <konstantin.ananyev@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] ipsec: fix use of uninitialized variable
>
> > -----Original Message-----
> > From: dev <dev-bounces@dpdk.org> On Behalf Of Konstantin Ananyev
> > Sent: Wednesday, February 19, 2020 12:23 AM
> > To: dev@dpdk.org
> > Cc: akhil.goyal@nxp.com; Ananyev, Konstantin
> > <konstantin.ananyev@intel.com>
> > Subject: [dpdk-dev] [PATCH] ipsec: fix use of uninitialized variable
> >
> > Defects reported by coverity scan
> > uninit_use_in_call: Using uninitialized element of array clen when
> > calling cpu_crypto_bulk.
> >
> > Coverity issue: 354233, 354234
> > Fixes: 957394f72658 ("ipsec: support CPU crypto mode")
> >
> > Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
>
> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
If possible can we get this merged into RC4.
next prev parent reply other threads:[~2020-02-19 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 0:23 Konstantin Ananyev
2020-02-19 14:14 ` Iremonger, Bernard
2020-02-19 15:27 ` Mcnamara, John [this message]
2020-02-20 10:36 ` Akhil Goyal
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=MWHPR1101MB21581AC3A635DB6AAD630661FC100@MWHPR1101MB2158.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.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).