From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Griffin, John" <john.griffin@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] crypto/qat: fix to avoid buffer overwrite in OOP case
Date: Fri, 16 Dec 2016 15:11:49 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476B3ADA@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <B35B4DC4161C394FB0B7D8F7C232B73C4D323707@irsmsx105.ger.corp.intel.com>
> -----Original Message-----
> From: Griffin, John
> Sent: Friday, December 16, 2016 11:21 AM
> To: Trahe, Fiona; dev@dpdk.org
> Cc: De Lara Guarch, Pablo; Trahe, Fiona; stable@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v2] crypto/qat: fix to avoid buffer overwrite
> in OOP case
>
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Fiona Trahe
> > Sent: Friday, December 9, 2016 3:39 PM
> > To: dev@dpdk.org
> > Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Trahe, Fiona
> > <fiona.trahe@intel.com>; stable@dpdk.org
> > Subject: [dpdk-dev] [PATCH v2] crypto/qat: fix to avoid buffer overwrite in
> > OOP case
> >
> > In out-of-place operation, data is DMAed from source mbuf to destination
> > mbuf. To avoid header data in dest mbuf being overwritten, the minimal
> data-
> > set should be DMAed.
> >
> > Fixes: 39e0bee48e81 ("crypto/qat: rework request builder for
> > performance")
> >
> > Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
> Acked-by: John Griffin <john.griffin@intel.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2016-12-16 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1479986267-2836-1-git-send-email-fiona.trahe@intel.com>
2016-12-09 15:39 ` [dpdk-stable] " Fiona Trahe
2016-12-16 11:20 ` [dpdk-stable] [dpdk-dev] " Griffin, John
2016-12-16 15:11 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D897476B3ADA@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@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).