linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Dave Chinner <david@fromorbit.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs_io: fix gcc-7 related printf warnings
Date: Thu, 9 Nov 2017 19:27:21 -0800	[thread overview]
Message-ID: <20171110032721.GB25227@magnolia> (raw)
In-Reply-To: <20171110032104.GA25227@magnolia>

On Thu, Nov 09, 2017 at 07:21:04PM -0800, Darrick J. Wong wrote:
> On Thu, Nov 09, 2017 at 07:43:59PM -0600, Eric Sandeen wrote:
> > On 11/9/17 7:39 PM, Dave Chinner wrote:
> > > 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>
> > 
> > 2^63 is 19 chars, yup.
> > 
> > Reviewed-by: Eric Sandeen <sandeen@sandeen.net>
> > 
> > > ---
> > >  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];
> 
> Waitaminute.  The longest format string is bbuf, which gets
> "[%lld..%lld]:".  The longest number %lld can print is
> "-9223372036854775807" which requires 20 bytes.  Therefore, bbuf needs
> 1 + 20 + 2 + 20 + 2 + 1 == 46 bytes, not 40.  rbuf and abuf have similar
> problems, though I guess a 48-byte string will work for all.
> 
> Granted, it's snprintf so it'll just truncate the second number if it
> has to, but seeing as this came from a gcc warning:
> 
> "fsmap.c:228:3: note: ‘snprintf’ output between 8 and 40 bytes into a
> destination of size 32"
> 
> So am I just bad at math, or is gcc wrong here?

Ah, dchinner points out on irc that gcc knows we (>> 9) the numbers
before printing them so the maximum value is 36028797018963967, so
40 bytes works.

gcc: 1, maintainer: 0

Looks ok,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>

--D

> --D
> 
> > >  	char			owner[OWNER_BUF_SZ];
> > >  	int			sunit, swidth;
> > >  	int			flg = 0;
> > > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2017-11-10  3:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10  1:39 [PATCH] xfs_io: fix gcc-7 related printf warnings Dave Chinner
2017-11-10  1:43 ` Eric Sandeen
2017-11-10  3:21   ` Darrick J. Wong
2017-11-10  3:27     ` Darrick J. Wong [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=20171110032721.GB25227@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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).