From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: dev@dpdk.org
Cc: daxuex.gao@intel.com, wisamm@nvidia.com, stable@dpdk.org
Subject: [PATCH] app/flow-perf: fix logic to add comma every three digits
Date: Sat, 11 Jun 2022 03:36:43 +0530 [thread overview]
Message-ID: <08953a79d2cf9a91cc687a25b964c52cf6bb3e09.1654898425.git.rahul.lakkireddy@chelsio.com> (raw)
Add comma after 1 in 1000 too, like 1,000. Also, since max uint64_t is
a 20 digit number, increase space in temporary array to hold 20 digits.
Fixes following warnings when using optimization=1 build flag with
GCC 11.
../app/test-flow-perf/main.c: In function ‘pretty_number’:
../app/test-flow-perf/main.c:1737:28: warning: ‘sprintf’ may write a terminating nul past the end of the destination [-Wformat-overflow=]
sprintf(p[i++], "%d", (int)n);
^
../app/test-flow-perf/main.c:1737:9: note: ‘sprintf’ output between 2 and 5 bytes into a destination of size 4
sprintf(p[i++], "%d", (int)n);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bugzilla ID: 1029
Fixes: 15c431864000 ("app/flow-perf: add packet forwarding support")
Cc: stable@dpdk.org
Reported-by: Daxue Gao <daxuex.gao@intel.com>
Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
---
app/test-flow-perf/main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/app/test-flow-perf/main.c b/app/test-flow-perf/main.c
index 56d43734e3..594507a85e 100644
--- a/app/test-flow-perf/main.c
+++ b/app/test-flow-perf/main.c
@@ -1724,11 +1724,11 @@ do_tx(struct lcore_info *li, uint16_t cnt, uint16_t tx_port,
static char *
pretty_number(uint64_t n, char *buf)
{
- char p[6][4];
+ char p[7][4];
int i = 0;
int off = 0;
- while (n > 1000) {
+ while (n >= 1000) {
sprintf(p[i], "%03d", (int)(n % 1000));
n /= 1000;
i += 1;
--
2.27.0
next reply other threads:[~2022-06-10 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 22:06 Rahul Lakkireddy [this message]
2022-06-10 23:45 ` Stephen Hemminger
2022-06-13 9:55 ` Rahul Lakkireddy
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=08953a79d2cf9a91cc687a25b964c52cf6bb3e09.1654898425.git.rahul.lakkireddy@chelsio.com \
--to=rahul.lakkireddy@chelsio.com \
--cc=daxuex.gao@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=wisamm@nvidia.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;
as well as URLs for NNTP newsgroup(s).