From: Wenwu Ma <wenwux.ma@intel.com>
To: ajit.khaparde@broadcom.com, somnath.kotur@broadcom.com,
amitprakashs@marvell.com, abhinandan.gujjar@intel.com,
dev@dpdk.org, stable@dpdk.org
Cc: tingtingx.liao@intel.com, Wenwu Ma <wenwux.ma@intel.com>
Subject: [PATCH 2/3] eventdev: fix uninitialized variable
Date: Mon, 25 Nov 2024 14:47:54 +0800 [thread overview]
Message-ID: <20241125064755.3943-3-wenwux.ma@intel.com> (raw)
In-Reply-To: <20241125064755.3943-1-wenwux.ma@intel.com>
This patch fixes the variable 'events' may be used uninitialized.
Fixes: 7901eac3409a ("eventdev: add crypto adapter implementation")
Cc: stable@dpdk.org
Signed-off-by: Wenwu Ma <wenwux.ma@intel.com>
---
lib/eventdev/rte_event_crypto_adapter.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/eventdev/rte_event_crypto_adapter.c b/lib/eventdev/rte_event_crypto_adapter.c
index 939ca1cad9..1ca839510b 100644
--- a/lib/eventdev/rte_event_crypto_adapter.c
+++ b/lib/eventdev/rte_event_crypto_adapter.c
@@ -685,6 +685,7 @@ eca_ops_enqueue_burst(struct event_crypto_adapter *adapter,
nb_ev = 0;
retry = 0;
nb_enqueued = 0;
+ memset(events, 0, sizeof(events));
num = RTE_MIN(num, BATCH_SIZE);
for (i = 0; i < num; i++) {
struct rte_event *ev = &events[nb_ev++];
--
2.34.1
next prev parent reply other threads:[~2024-11-25 7:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 6:47 [PATCH 0/3] fix uninitialized variable Wenwu Ma
2024-11-25 6:47 ` [PATCH 1/3] net/bnxt: " Wenwu Ma
2024-11-25 6:47 ` Wenwu Ma [this message]
2024-11-27 10:49 ` [PATCH 2/3] eventdev: " Gujjar, Abhinandan S
2024-11-25 6:47 ` [PATCH 3/3] " Wenwu Ma
2024-11-27 2:46 ` Liao, TingtingX
2026-01-13 20:04 ` Stephen Hemminger
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=20241125064755.3943-3-wenwux.ma@intel.com \
--to=wenwux.ma@intel.com \
--cc=abhinandan.gujjar@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=amitprakashs@marvell.com \
--cc=dev@dpdk.org \
--cc=somnath.kotur@broadcom.com \
--cc=stable@dpdk.org \
--cc=tingtingx.liao@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 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.