From: fengchengwen <fengchengwen@huawei.com>
To: Stephen Hemminger <stephen@networkplumber.org>, <dev@dpdk.org>
Cc: <stable@dpdk.org>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v3 5/6] test: fix impossible format-truncation in cfgfiles
Date: Tue, 18 Nov 2025 10:22:35 +0800 [thread overview]
Message-ID: <79049dc3-8c0b-41f2-bb02-73c18766377c@huawei.com> (raw)
In-Reply-To: <20251117175332.14014-6-stephen@networkplumber.org>
On 11/18/2025 1:52 AM, Stephen Hemminger wrote:
> Although, it is not possible on Linux (which always uses /tmp)
> the compiler complains about possible snprintf() truncation.
> Simplest fix is to just increase the size of the filename variable.
>
> Fixes: be22019a58c4 ("test: restore cfgfile tests")
> Cc: stable@dpdk.org
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> app/test/test_cfgfile.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/app/test/test_cfgfile.c b/app/test/test_cfgfile.c
> index b189d9d7a5..823b48e1fa 100644
> --- a/app/test/test_cfgfile.c
> +++ b/app/test/test_cfgfile.c
> @@ -148,7 +148,7 @@ static int
> test_cfgfile_realloc_sections(void)
> {
> struct rte_cfgfile *cfgfile;
> - char filename[PATH_MAX];
> + char filename[PATH_MAX + NAME_MAX];
there are many other function invoke make_tmp_file(), such as test_cfgfile_invalid_section_header.
I think we could modify make_tmp_file(): snprintf(filename, PATH_MAX - NAME_MAX, ...).
> int ret;
> const char *value;
>
prev parent reply other threads:[~2025-11-18 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251115193409.99740-1-stephen@networkplumber.org>
[not found] ` <20251117175332.14014-1-stephen@networkplumber.org>
2025-11-17 17:52 ` [PATCH v3 4/6] test: fix format overflow warning in ACL test Stephen Hemminger
2025-11-17 17:52 ` [PATCH v3 5/6] test: fix impossible format-truncation in cfgfiles Stephen Hemminger
2025-11-18 2:22 ` fengchengwen [this message]
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=79049dc3-8c0b-41f2-bb02-73c18766377c@huawei.com \
--to=fengchengwen@huawei.com \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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).