From: Akhil Goyal <akhil.goyal@nxp.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "marko.kovacevic@intel.com" <marko.kovacevic@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] fips_validation: fix auth verify
Date: Mon, 18 Nov 2019 07:09:58 +0000 [thread overview]
Message-ID: <VE1PR04MB6639F5F78E0196E26F0B158FE64D0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20191106105425.1061-1-roy.fan.zhang@intel.com>
Hi Marko,
Could you please ack this patch if no issues.
>
> Fixes: f64adb6714e0 ("examples/fips_validation: support HMAC parsing")
> Cc: marko.kovacevic@intel.com
> Cc: stable@dpdk.org
>
> This patch fixes the incorrect mbuf write and digest memory leak in
> fips_validation authentication verify.
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
Regards,
Akhil
next prev parent reply other threads:[~2019-11-18 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 10:54 Fan Zhang
2019-11-18 7:09 ` Akhil Goyal [this message]
2019-11-18 16:43 ` Kovacevic, Marko
2019-11-19 7:53 ` 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=VE1PR04MB6639F5F78E0196E26F0B158FE64D0@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=marko.kovacevic@intel.com \
--cc=roy.fan.zhang@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).