From: Akhil Goyal <akhil.goyal@nxp.com>
To: "Nowak, DamianX" <damianx.nowak@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/qat: fix seg-fault
Date: Thu, 18 Jul 2019 15:23:44 +0000 [thread overview]
Message-ID: <VE1PR04MB66394432AA2C4773A695C511E6C80@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <6976F642F4CB7B4C9D17DE41C99F326055D07757@hasmsx107.ger.corp.intel.com>
>
> >
> > Fix for seg-faults occurring:
> > 1) in buffer re-alignment in-place sgl case
> > 2) case where data end is exactly at end of an sgl segment.
> > Also renamed variable and increased comments for clearer code.
> >
> > Fixes: 40002f6c2a24 ("crypto/qat: extend support for digest-encrypted auth-
> > cipher")
> >
> > Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
>
> Acked-by: Damian Nowak <damianx.nowak@intel.com>
Applied to dpdk-next-crypto
Thanks
prev parent reply other threads:[~2019-07-18 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 9:53 Fiona Trahe
2019-07-10 10:10 ` Ananyev, Konstantin
2019-07-10 15:03 ` Nowak, DamianX
2019-07-18 15:23 ` 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=VE1PR04MB66394432AA2C4773A695C511E6C80@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=damianx.nowak@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--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).