DPDK patches and discussions
 help / color / mirror / Atom feed
From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: fiona.trahe@intel.com, pablo.de.lara.guarch@intel.com,
	john.griffin@intel.com, deepak.k.jain@intel.com,
	abhinav.singh@intel.com,
	Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-dev] [PATCH] crypto/qat: fix AES-GMAC length of data
Date: Tue, 11 Jul 2017 14:35:34 +0100	[thread overview]
Message-ID: <1499780135-28975-1-git-send-email-arkadiuszx.kusztal@intel.com> (raw)

Fix AES-GMAC length of the data copied to the hardware to avoid
copying more data than necessary.

Fixes: 2fa64f840d65 ("crypto/qat: add GMAC capability")

Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
---
 drivers/crypto/qat/qat_crypto.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/crypto/qat/qat_crypto.c b/drivers/crypto/qat/qat_crypto.c
index 7e04f21..6764553 100644
--- a/drivers/crypto/qat/qat_crypto.c
+++ b/drivers/crypto/qat/qat_crypto.c
@@ -1363,10 +1363,10 @@ qat_write_hw_desc_entry(struct rte_crypto_op *op, uint8_t *out_msg,
 		if (!do_aead) {
 			qat_req->comn_mid.dst_length =
 				qat_req->comn_mid.src_length =
-					rte_pktmbuf_data_len(op->sym->m_src);
+					op->sym->auth.data.length;
 			auth_param->u1.aad_adr = 0;
 			auth_param->auth_len = op->sym->auth.data.length;
-			auth_param->auth_off = op->sym->auth.data.offset;
+			auth_param->auth_off = 0;
 			auth_param->u2.aad_sz = 0;
 		}
 	}
-- 
2.1.0

             reply	other threads:[~2017-07-11 13:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 13:35 Arek Kusztal [this message]
2017-07-11 13:35 ` [dpdk-dev] [PATCH] crypto/qat: remove unused ablkcipher struct and functions Arek Kusztal
2017-07-11 13:44   ` Trahe, Fiona
2017-07-11 14:02     ` De Lara Guarch, Pablo
2017-07-11 13:46 ` [dpdk-dev] [PATCH] crypto/qat: fix AES-GMAC length of data Trahe, Fiona

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=1499780135-28975-1-git-send-email-arkadiuszx.kusztal@intel.com \
    --to=arkadiuszx.kusztal@intel.com \
    --cc=abhinav.singh@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=john.griffin@intel.com \
    --cc=pablo.de.lara.guarch@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).