From: David Laight <David.Laight@ACULAB.COM>
To: 'Song Liu' <songliubraving@fb.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: stable <stable@vger.kernel.org>,
Jin Yao <yao.jin@linux.intel.com>, "Jiri Olsa" <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>
Subject: RE: [PATCH] perf: increase size of buf in perf_evsel__hists_browse()
Date: Sat, 31 Oct 2020 11:27:13 +0000 [thread overview]
Message-ID: <5334209cb6fa4a0782029ca7b44c917e@AcuMS.aculab.com> (raw)
In-Reply-To: <20201030235431.534417-1-songliubraving@fb.com>
From: Song Liu
> Sent: 30 October 2020 23:55
>
> Making perf with gcc-9.1.1 generates the following warning:
>
> CC ui/browsers/hists.o
> ui/browsers/hists.c: In function 'perf_evsel__hists_browse':
> ui/browsers/hists.c:3078:61: error: '%d' directive output may be \
> truncated writing between 1 and 11 bytes into a region of size \
> between 2 and 12 [-Werror=format-truncation=]
>
> 3078 | "Max event group index to sort is %d (index from 0 to %d)",
> | ^~
> ui/browsers/hists.c:3078:7: note: directive argument in the range [-2147483648, 8]
> 3078 | "Max event group index to sort is %d (index from 0 to %d)",
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> In file included from /usr/include/stdio.h:937,
> from ui/browsers/hists.c:5:
>
> IOW, the string in line 3078 might be too long for buf[] of 64 bytes.
>
> Fix this by increasing the size of buf[] to 128.
ISTM that something should be unsigned so that the bound check
that puts an upper bound of 8 implies a lower bound.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-10-31 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 23:54 Song Liu
2020-10-31 11:27 ` David Laight [this message]
2020-11-01 18:06 ` Song Liu
2020-10-31 20:29 ` Jiri Olsa
2020-11-03 12:13 ` Arnaldo Carvalho de Melo
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=5334209cb6fa4a0782029ca7b44c917e@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=stable@vger.kernel.org \
--cc=yao.jin@linux.intel.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
Powered by JetHome