From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH] xfs_io: fix gcc-7 related printf warnings
Date: Fri, 10 Nov 2017 12:39:26 +1100 [thread overview]
Message-ID: <20171110013926.15289-1-david@fromorbit.com> (raw)
From: Dave Chinner <dchinner@redhat.com>
New compiler, new checks, new warnings.
Fix the new [-Wformat-truncation=] warnings that io/fsmap.c is
throwing w/ gcc-7.2 because "%lld..%lld" requires a buffer 40
characters long, not 32.
Signed-Off-By: Dave Chinner <dchinner@redhat.com>
---
io/fsmap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/io/fsmap.c b/io/fsmap.c
index 448fb5356466..e46fdbaa148c 100644
--- a/io/fsmap.c
+++ b/io/fsmap.c
@@ -184,8 +184,8 @@ dump_map_verbose(
off64_t agoff, bperag;
int foff_w, boff_w, aoff_w, tot_w, agno_w, own_w;
int nr_w, dev_w;
- char rbuf[32], bbuf[32], abuf[32], obuf[32];
- char nbuf[32], dbuf[32], gbuf[32];
+ char rbuf[40], bbuf[40], abuf[40], obuf[40];
+ char nbuf[40], dbuf[40], gbuf[40];
char owner[OWNER_BUF_SZ];
int sunit, swidth;
int flg = 0;
--
2.15.0
next reply other threads:[~2017-11-10 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 1:39 Dave Chinner [this message]
2017-11-10 1:43 ` [PATCH] xfs_io: fix gcc-7 related printf warnings Eric Sandeen
2017-11-10 3:21 ` Darrick J. Wong
2017-11-10 3:27 ` Darrick J. Wong
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=20171110013926.15289-1-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.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).