From: Khem Raj <raj.khem@gmail.com>
To: Ian Rogers <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH] perf cpumap: Make counter as unsigned ints
Date: Wed, 25 Jan 2023 11:04:13 -0800 [thread overview]
Message-ID: <CAMKF1soqvBXcGUjpkN6wuxV8kZbFmqYBwB02Q5PB6qBAinjvOQ@mail.gmail.com> (raw)
In-Reply-To: <CAP-5=fWoQrn3i-Vpec0w8y4djq=PLhbR6TTeQ4XxKaR-bBDZAw@mail.gmail.com>
On Tue, Jan 24, 2023 at 9:02 AM Ian Rogers <irogers@google.com> wrote:
>
> On Mon, Jan 23, 2023 at 1:13 PM Khem Raj <raj.khem@gmail.com> wrote:
> >
> > These are loop counters which is inherently unsigned. Therefore make
> > them unsigned. Moreover it also fixes alloc-size-larger-than
> > error with gcc-13, where malloc can be called with (-1) due to tmp_len
> > being an int type.
> >
> > Fixes
> > | cpumap.c:366:20: error: argument 1 range [18446744065119617024, 18446744073709551612] exceeds maximum object size 9223372036854775807 [-Werror=alloc-size-larger-than=]
> > | 366 | tmp_cpus = malloc(tmp_len * sizeof(struct perf_cpu));
> > | | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > Cc: Peter Zijlstra <peterz@infradead.org>
> > Cc: Ingo Molnar <mingo@redhat.com>
> > Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> > Cc: Mark Rutland <mark.rutland@arm.com>
> > Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> > Cc: Jiri Olsa <jolsa@kernel.org>
> > Cc: Namhyung Kim <namhyung@kernel.org>
> > ---
> > tools/lib/perf/cpumap.c | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/tools/lib/perf/cpumap.c b/tools/lib/perf/cpumap.c
> > index 6cd0be7c1bb4..d960880dd903 100644
> > --- a/tools/lib/perf/cpumap.c
> > +++ b/tools/lib/perf/cpumap.c
> > @@ -351,8 +351,8 @@ struct perf_cpu_map *perf_cpu_map__merge(struct perf_cpu_map *orig,
> > struct perf_cpu_map *other)
> > {
> > struct perf_cpu *tmp_cpus;
> > - int tmp_len;
> > - int i, j, k;
> > + unsigned int tmp_len;
> > + unsigned int i, j, k;
> > struct perf_cpu_map *merged;
> >
> > if (perf_cpu_map__is_subset(orig, other))
> > @@ -369,7 +369,7 @@ struct perf_cpu_map *perf_cpu_map__merge(struct perf_cpu_map *orig,
> >
> > /* Standard merge algorithm from wikipedia */
> > i = j = k = 0;
> > - while (i < orig->nr && j < other->nr) {
> > + while (i < (unsigned int)orig->nr && j < (unsigned int)other->nr) {
>
> Rather than cast 'nr' why not add the unsigned to the declaration?
>
if type of nr is changed from int to unsigned int, this will ensue a
lot of changes including function signature changes, I am not
sure if that is the best approach.
> Thanks,
> Ian
>
> > if (orig->map[i].cpu <= other->map[j].cpu) {
> > if (orig->map[i].cpu == other->map[j].cpu)
> > j++;
> > @@ -378,10 +378,10 @@ struct perf_cpu_map *perf_cpu_map__merge(struct perf_cpu_map *orig,
> > tmp_cpus[k++] = other->map[j++];
> > }
> >
> > - while (i < orig->nr)
> > + while (i < (unsigned int)orig->nr)
> > tmp_cpus[k++] = orig->map[i++];
> >
> > - while (j < other->nr)
> > + while (j < (unsigned int)other->nr)
> > tmp_cpus[k++] = other->map[j++];
> > assert(k <= tmp_len);
> >
> > --
> > 2.39.1
> >
next prev parent reply other threads:[~2023-01-25 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 21:13 [PATCH] perf cpumap: Make counter as unsigned ints Khem Raj
2023-01-24 17:02 ` Ian Rogers
2023-01-25 19:04 ` Khem Raj [this message]
2023-01-25 20:59 ` Ian Rogers
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=CAMKF1soqvBXcGUjpkN6wuxV8kZbFmqYBwB02Q5PB6qBAinjvOQ@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).