[dpdk-stable] [PATCH 17.11] crypto/qat: fix null auth issues when using vfio_pci
Arek Kusztal
arkadiuszx.kusztal at intel.com
Wed Jan 8 16:33:01 CET 2020
[ upstream commit 65beb9abca6dbb2167a53ab31d79e03f0857357b ]
When running auth NULL cases while using vfio_pci,
DMAR read/write faults appear. It happens even if
digest_length is set to 0. This is caused by auth_res_addr
initialized as 0x0.
Fixes: 4e0955bddb08
Cc: stable at dpdk.org
Signed-off-by: Damian Nowak <damianx.nowak at intel.com>
Signed-off-by: Arek Kusztal <arkadiuszx.kusztal at intel.com>
---
drivers/crypto/qat/qat_crypto.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/crypto/qat/qat_crypto.c b/drivers/crypto/qat/qat_crypto.c
index 85a9ba0..05b37e6 100644
--- a/drivers/crypto/qat/qat_crypto.c
+++ b/drivers/crypto/qat/qat_crypto.c
@@ -1370,10 +1370,8 @@ qat_write_hw_desc_entry(struct rte_crypto_op *op, uint8_t *out_msg,
}
min_ofs = auth_ofs;
-
- if (likely(ctx->qat_hash_alg != ICP_QAT_HW_AUTH_ALGO_NULL))
- auth_param->auth_res_addr =
- op->sym->auth.digest.phys_addr;
+ auth_param->auth_res_addr =
+ op->sym->auth.digest.phys_addr;
}
--
2.1.0
More information about the stable
mailing list