All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Griffin, John" <john.griffin@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH v2] crypto/qat: fix to avoid buffer overwrite in	OOP case
Date: Fri, 16 Dec 2016 11:20:56 +0000	[thread overview]
Message-ID: <B35B4DC4161C394FB0B7D8F7C232B73C4D323707@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <1481297945-20649-1-git-send-email-fiona.trahe@intel.com>



> -----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>

  reply	other threads:[~2016-12-16 11:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 11:17 [PATCH] crypto/qat: fix to avoid buffer overwrite in OOP case Fiona Trahe
2016-12-09 12:05 ` De Lara Guarch, Pablo
2016-12-09 15:39 ` [PATCH v2] " Fiona Trahe
2016-12-16 11:20   ` Griffin, John [this message]
2016-12-16 15:11     ` De Lara Guarch, Pablo

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=B35B4DC4161C394FB0B7D8F7C232B73C4D323707@irsmsx105.ger.corp.intel.com \
    --to=john.griffin@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=pablo.de.lara.guarch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.