From: Stephen Hemminger <stephen@networkplumber.org>
To: Shani Peretz <shperetz@nvidia.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>, Remy Horton <remy.horton@intel.com>
Subject: Re: [PATCH v2] examples/ethtool: fix buffer size for pkt pool name
Date: Mon, 22 Dec 2025 15:31:14 -0800 [thread overview]
Message-ID: <20251222153114.24314d10@phoenix.local> (raw)
In-Reply-To: <20251222083858.1035980-1-shperetz@nvidia.com>
On Mon, 22 Dec 2025 10:38:58 +0200
Shani Peretz <shperetz@nvidia.com> wrote:
> Use RTE_MEMPOOL_NAMESIZE for str_name buffer size instead of the
> hardcoded value 16, which was insufficient as the format
> string "pkt_pool%i" can produce up to 19 bytes (8 for "pkt_pool",
> up to 10 for integer value, and 1 for null terminator).
>
> Fixes: bda68ab9d1e7 ("examples/ethtool: add user-space ethtool sample application")
> Cc: stable@dpdk.org
>
> Signed-off-by: Shani Peretz <shperetz@nvidia.com>
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
prev parent reply other threads:[~2025-12-22 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 11:01 [PATCH] " Shani Peretz
2025-12-03 15:20 ` Stephen Hemminger
2025-12-22 8:38 ` [PATCH v2] " Shani Peretz
2025-12-22 23:31 ` Stephen Hemminger [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=20251222153114.24314d10@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=remy.horton@intel.com \
--cc=shperetz@nvidia.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).