From: Namhyung Kim <namhyung@kernel.org>
To: Yunseong Kim <yskelg@gmail.com>
Cc: Ian Rogers <irogers@google.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>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Yang Jihong <yangjihong1@huawei.com>,
Ze Gao <zegao2021@gmail.com>, Leo Yan <leo.yan@linux.dev>,
Ravi Bangoria <ravi.bangoria@amd.com>,
Austin Kim <austindh.kim@gmail.com>,
shjy180909@gmail.com,
linux-perf-users <linux-perf-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] util: constant -1 with expression of type char and allocation failure handling
Date: Mon, 24 Jun 2024 22:00:33 -0700 [thread overview]
Message-ID: <ZnpO8TKWSiterMwC@google.com> (raw)
In-Reply-To: <5c1f3b54-da71-47b7-a30c-0011a23195c8@gmail.com>
Hello,
On Thu, Jun 20, 2024 at 04:10:53AM +0900, Yunseong Kim wrote:
> Hi Ian,
>
> On 6/20/24 4:03 오전, Ian Rogers wrote:
> >
> >
> > On Wed, Jun 19, 2024, 11:39 AM <yskelg@gmail.com
> > <mailto:yskelg@gmail.com>> wrote:
> >
> > From: Yunseong Kim <yskelg@gmail.com <mailto:yskelg@gmail.com>>
> >
> > This patch resolve this warning.
> >
> > tools/perf/util/evsel.c:1620:9: error: result of comparison of constant
> > -1 with expression of type 'char' is always false
> > -Werror,-Wtautological-constant-out-of-range-compare
> > 1620 | if (c == -1)
> > | ~ ^ ~~
> >
> > Add handling on unread_unwind_spec_debug_frame().
> > This make caller find_proc_info() works well when the allocation
> > failure.
> >
> > Signed-off-by: Yunseong Kim <yskelg@gmail.com <mailto:yskelg@gmail.com>>
> >
> >
> >
> > Both changes look good. Could you make them 2 commits? If so add my:
>
> No problem! I'll send it right away.
>
> Thank you for the code review.
>
> > Reviewed-by: Ian Rogers <irogers@google.com <mailto:irogers@google.com>>
You forgot to add Ian's Reviewed-by in the next patches.
I can add it to them this time, but please do so next time.
Thanks,
Namhyung
> >
> > Thanks,
> > Ian
> >
> > ---
> > tools/perf/util/evsel.c | 2 +-
> > tools/perf/util/unwind-libunwind-local.c | 5 +++++
> > 2 files changed, 6 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
> > index 25857894c047..bc603193c477 100644
> > --- a/tools/perf/util/evsel.c
> > +++ b/tools/perf/util/evsel.c
> > @@ -1620,7 +1620,7 @@ static int evsel__read_group(struct evsel
> > *leader, int cpu_map_idx, int thread)
> >
> > static bool read_until_char(struct io *io, char e)
> > {
> > - char c;
> > + int c;
> >
> > do {
> > c = io__get_char(io);
> > diff --git a/tools/perf/util/unwind-libunwind-local.c
> > b/tools/perf/util/unwind-libunwind-local.c
> > index cde267ea3e99..a424eae6d308 100644
> > --- a/tools/perf/util/unwind-libunwind-local.c
> > +++ b/tools/perf/util/unwind-libunwind-local.c
> > @@ -390,6 +390,11 @@ static int read_unwind_spec_debug_frame(struct
> > dso *dso,
> > char *debuglink = malloc(PATH_MAX);
> > int ret = 0;
> >
> > + if (debuglink == NULL) {
> > + pr_err("unwind: Can't read unwind
> > spec debug frame.\n");
> > + return -ENOMEM;
> > + }
> > +
> > ret = dso__read_binary_type_filename(
> > dso, DSO_BINARY_TYPE__DEBUGLINK,
> > machine->root_dir, debuglink, PATH_MAX);
> > --
> > 2.44.0
> >
>
> Warm Regards,
> Yunseong Kim
next prev parent reply other threads:[~2024-06-25 5:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 18:38 yskelg
[not found] ` <CAP-5=fWm-Tij+vjqOa-18RsiO+1_ytWnKkDvp3vz5hv1O9aMCw@mail.gmail.com>
2024-06-19 19:10 ` Yunseong Kim
2024-06-25 5:00 ` Namhyung Kim [this message]
2024-06-25 5:22 ` Yunseong Kim
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=ZnpO8TKWSiterMwC@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=austindh.kim@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ravi.bangoria@amd.com \
--cc=shjy180909@gmail.com \
--cc=yangjihong1@huawei.com \
--cc=yskelg@gmail.com \
--cc=zegao2021@gmail.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
all inboxes | Powered by JetHome®