From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
stable@dpdk.org, Anatoly Burakov <anatoly.burakov@intel.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [PATCH v5 5/8] test: fix format overflow warning in ACL test
Date: Fri, 21 Nov 2025 09:08:24 -0800 [thread overview]
Message-ID: <20251121170947.134502-6-stephen@networkplumber.org> (raw)
In-Reply-To: <20251121170947.134502-1-stephen@networkplumber.org>
This test has an array of input lines, but the two dimensional
array confuses compiler length checks. Convert to an array
of pointers to fixed strings which avoids the problem.
Make both variables static since not shared with other code.
Fixes: 5205954791cb ("app/test: packet framework unit tests")
Cc: stable@dpdk.org
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
app/test/test_table_acl.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/app/test/test_table_acl.c b/app/test/test_table_acl.c
index dff9bddfb9..94edf37234 100644
--- a/app/test/test_table_acl.c
+++ b/app/test/test_table_acl.c
@@ -317,7 +317,7 @@ parse_cb_ipv4_rule_del(char *str, struct rte_table_acl_rule_delete_params *v)
* separated by ' : ', just ':'. It's a lot more readable and
* cleaner, IMO.
*/
-char lines[][128] = {
+static const char * const lines[] = {
"@0.0.0.0/0 0.0.0.0/0 0:65535 0:65535 2/0xff", /* Protocol check */
"@192.168.3.1/32 0.0.0.0/0 0:65535 0:65535 0/0", /* Src IP checl */
"@0.0.0.0/0 10.4.4.1/32 0:65535 0:65535 0/0", /* dst IP check */
@@ -325,7 +325,7 @@ char lines[][128] = {
"@0.0.0.0/0 0.0.0.0/0 0:65535 206:206 0/0", /* dst port check */
};
-char line[128];
+static char line[128];
static int
--
2.51.0
next prev parent reply other threads:[~2025-11-21 17:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251110182209.104087-1-stephen@networkplumber.org>
2025-11-10 18:19 ` [PATCH 1/3] examples/server_node_efd: fix format overflow Stephen Hemminger
2025-11-10 18:19 ` [PATCH 2/3] examples/vdpa: fix format overflow warning Stephen Hemminger
[not found] ` <20251111221857.443752-1-stephen@networkplumber.org>
2025-11-11 22:17 ` [PATCH v2 1/7] examples/server_node_efd: fix format overflow Stephen Hemminger
2025-11-11 22:17 ` [PATCH v2 2/7] examples/vdpa: fix format overflow warning Stephen Hemminger
2025-11-14 15:59 ` Bruce Richardson
[not found] ` <20251115193749.101355-1-stephen@networkplumber.org>
2025-11-15 19:36 ` [PATCH v3 1/4] examples/server_node_efd: fix format overflow Stephen Hemminger
2025-11-17 8:50 ` Bruce Richardson
2025-11-15 19:36 ` [PATCH v3 2/4] examples/vdpa: fix format overflow warning Stephen Hemminger
2025-11-19 4:31 ` Thomas Monjalon
2025-11-19 9:13 ` Bruce Richardson
[not found] ` <20251120162327.78062-1-stephen@networkplumber.org>
2025-11-20 16:21 ` [PATCH v4 1/4] examples/server_node_efd: fix format overflow Stephen Hemminger
2025-11-20 16:22 ` [PATCH v4 2/4] examples/vdpa: fix format overflow warning Stephen Hemminger
[not found] ` <20251121170947.134502-1-stephen@networkplumber.org>
2025-11-21 17:08 ` Stephen Hemminger [this message]
2025-11-21 17:08 ` [PATCH v5 6/8] test: fix impossible format-truncation in cfgfiles Stephen Hemminger
[not found] ` <20251123174503.20880-1-stephen@networkplumber.org>
2025-11-23 17:43 ` [PATCH v6 5/9] test: fix format overflow warning in ACL test Stephen Hemminger
2025-11-23 17:43 ` [PATCH v6 6/9] test: fix impossible format-truncation in cfgfiles 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=20251121170947.134502-6-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stable@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).