From: Maxime Leroy <maxime@leroys.fr>
To: dev@dpdk.org
Cc: vladimir.medvedkin@intel.com, rjarry@redhat.com,
Maxime Leroy <maxime@leroys.fr>
Subject: [RFC 1/5] test/fib6: zero-initialize config struct
Date: Tue, 31 Mar 2026 23:41:13 +0200 [thread overview]
Message-ID: <20260331214117.142495-2-maxime@leroys.fr> (raw)
In-Reply-To: <20260331214117.142495-1-maxime@leroys.fr>
Initialize rte_fib6_conf with { 0 } to avoid using uninitialized
fields, aligned with how it is already done in test_fib.c.
This is needed because the struct will gain new optional fields
(tbl8_pool) that must default to NULL.
Signed-off-by: Maxime Leroy <maxime@leroys.fr>
---
app/test/test_fib6.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/app/test/test_fib6.c b/app/test/test_fib6.c
index fffb590dbf..9fbdde6b05 100644
--- a/app/test/test_fib6.c
+++ b/app/test/test_fib6.c
@@ -38,7 +38,7 @@ int32_t
test_create_invalid(void)
{
struct rte_fib6 *fib = NULL;
- struct rte_fib6_conf config;
+ struct rte_fib6_conf config = { 0 };
config.max_routes = MAX_ROUTES;
config.rib_ext_sz = 0;
@@ -97,7 +97,7 @@ int32_t
test_multiple_create(void)
{
struct rte_fib6 *fib = NULL;
- struct rte_fib6_conf config;
+ struct rte_fib6_conf config = { 0 };
int32_t i;
config.rib_ext_sz = 0;
@@ -124,7 +124,7 @@ int32_t
test_free_null(void)
{
struct rte_fib6 *fib = NULL;
- struct rte_fib6_conf config;
+ struct rte_fib6_conf config = { 0 };
config.max_routes = MAX_ROUTES;
config.rib_ext_sz = 0;
@@ -148,7 +148,7 @@ int32_t
test_add_del_invalid(void)
{
struct rte_fib6 *fib = NULL;
- struct rte_fib6_conf config;
+ struct rte_fib6_conf config = { 0 };
uint64_t nh = 100;
struct rte_ipv6_addr ip = RTE_IPV6_ADDR_UNSPEC;
int ret;
@@ -342,7 +342,7 @@ int32_t
test_lookup(void)
{
struct rte_fib6 *fib = NULL;
- struct rte_fib6_conf config;
+ struct rte_fib6_conf config = { 0 };
uint64_t def_nh = 100;
int ret;
--
2.43.0
next prev parent reply other threads:[~2026-03-31 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 21:41 [RFC 0/5] fib: shared and resizable tbl8 pool Maxime Leroy
2026-03-31 21:41 ` Maxime Leroy [this message]
2026-03-31 21:41 ` [RFC 2/5] fib: share tbl8 definitions between fib and fib6 Maxime Leroy
2026-03-31 21:41 ` [RFC 3/5] fib: add shared tbl8 pool Maxime Leroy
2026-03-31 21:41 ` [RFC 4/5] fib: add resizable " Maxime Leroy
2026-03-31 21:41 ` [RFC 5/5] fib: add tbl8 pool stats API Maxime Leroy
2026-03-31 22:17 ` [RFC 0/5] fib: shared and resizable tbl8 pool Robin Jarry
2026-04-01 9:15 ` Maxime Leroy
2026-03-31 22:30 ` 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=20260331214117.142495-2-maxime@leroys.fr \
--to=maxime@leroys.fr \
--cc=dev@dpdk.org \
--cc=rjarry@redhat.com \
--cc=vladimir.medvedkin@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