From 099db3d156038b792d97c29a6e2743369d7d50a5 Mon Sep 17 00:00:00 2001 From: Kevin Traynor Date: Fri, 14 May 2021 16:08:34 +0100 Subject: [PATCH] crypto/zuc: fix build with GCC 11 GCC 11 complains that some arrays may be uninitialized in process_zuc_hash_op(). This is because their initialization depends on num_ops being > 0. This function is only called with num_ops > 0 because of checks in process_zuc_hash_op(). To remove the warning initialize the arrays. Fixes: 0b133c36ad7d ("crypto/zuc: support IPsec Multi-buffer lib v0.54") Cc: stable@dpdk.org Signed-off-by: Kevin Traynor --- drivers/crypto/zuc/rte_zuc_pmd.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/crypto/zuc/rte_zuc_pmd.c b/drivers/crypto/zuc/rte_zuc_pmd.c index aa50c12da6..42b669f188 100644 --- a/drivers/crypto/zuc/rte_zuc_pmd.c +++ b/drivers/crypto/zuc/rte_zuc_pmd.c @@ -238,11 +238,11 @@ process_zuc_hash_op(struct zuc_qp *qp, struct rte_crypto_op **ops, { unsigned int i; uint8_t processed_ops = 0; - uint8_t *src[ZUC_MAX_BURST]; + uint8_t *src[ZUC_MAX_BURST] = { 0 }; uint32_t *dst[ZUC_MAX_BURST]; - uint32_t length_in_bits[ZUC_MAX_BURST]; - uint8_t *iv[ZUC_MAX_BURST]; - const void *hash_keys[ZUC_MAX_BURST]; + uint32_t length_in_bits[ZUC_MAX_BURST] = { 0 }; + uint8_t *iv[ZUC_MAX_BURST] = { 0 }; + const void *hash_keys[ZUC_MAX_BURST] = { 0 }; struct zuc_session *sess; for (i = 0; i < num_ops; i++) { -- 2.20.1