[RFC 2/5] crypto/qat: use secure memset

[Stephen Hemminger <stephen@networkplumber.org>]

Regular memset maybe removed by compiler if done before a free
function. Use the C11 memset_s instead to ensure security
parameters are cleared.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 drivers/crypto/qat/qat_asym.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/crypto/qat/qat_asym.c b/drivers/crypto/qat/qat_asym.c
index f5b56b2f71..a2b87ddbfd 100644
--- a/drivers/crypto/qat/qat_asym.c
+++ b/drivers/crypto/qat/qat_asym.c
@@ -103,7 +103,7 @@ static const struct rte_driver cryptodev_qat_asym_driver = {
 
 #define PARAM_CLR(what) \
 	do { \
-		memset(what.data, 0, what.length); \
+		memset_s(what.data, 0, what.length); \
 		rte_free(what.data);	\
 	} while (0)
 
-- 
2.45.2