From: German Gomez <german.gomez@arm.com>
To: Miaoqian Lin <linmq006@gmail.com>
Cc: 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@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>, Andi Kleen <ak@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf expr: Fix return value of ids__new
Date: Mon, 13 Dec 2021 13:13:47 +0000 [thread overview]
Message-ID: <d0fabb42-399f-2b72-412b-4f5ba6b9eea4@arm.com> (raw)
In-Reply-To: <20211213070956.15119-1-linmq006@gmail.com>
Hi Miaoqian,
Fails to build due to missing import: "#import <linux/err.h>".
Could you please verify?
Other than that, it looks good to me. I shared the testing below:
On 13/12/2021 07:09, Miaoqian Lin wrote:
> callers of ids__new() function only do NULL checking for the return
> value. ids__new() calles hashmap__new(), which may return
> ERR_PTR(-ENOMEM). Instead of changing the checking one-by-one.
> return NULL instead of ERR_PTR(-ENOMEM) to keep
> consistent.
>
> Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
> ---
> tools/perf/util/expr.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/expr.c b/tools/perf/util/expr.c
> index 1d532b9fed29..aabdc112300c 100644
> --- a/tools/perf/util/expr.c
> +++ b/tools/perf/util/expr.c
> @@ -65,7 +65,13 @@ static bool key_equal(const void *key1, const void *key2,
>
> struct hashmap *ids__new(void)
> {
> - return hashmap__new(key_hash, key_equal, NULL);
> + struct hashmap *hash;
> +
> + hash = hashmap__new(key_hash, key_equal, NULL);
> + if (IS_ERR(hash))
> + return NULL;
> + else
> + return hash;
> }
>
> void ids__free(struct hashmap *ids)
Before this patch, perf-test was segfaulting instead of a graceful fail.
I think this could have been an issue in the perf tool as well.
(I forced hashmap__new in "tools/perf/util/hashmap.c" to always return
the error for the purposes of the test).
$ make DEBUG=1 NO_LIBBPF=1 # builds with tools/perf/util/hashmap.c
$ ./perf test 7 -v
Couldn't bump rlimit(MEMLOCK), failures may take place when creating BPF maps, etc
7: Simple expression parser :
--- start ---
test child forked, pid 1953536
perf: Segmentation fault
Obtained 16 stack frames.
./perf(dump_stack+0x31) [0x559222b3ae48]
./perf(sighandler_dump_stack+0x33) [0x559222b3af30]
/lib/x86_64-linux-gnu/libc.so.6(+0x4620f) [0x7ff81df6220f]
./perf(hashmap__size+0x23) [0x559222bf9f47]
./perf(ids__union+0x5f) [0x559222be1f0e]
./perf(+0x2d9ba8) [0x559222ac7ba8]
./perf(+0x2da223) [0x559222ac8223]
./perf(+0x2a5fe9) [0x559222a93fe9]
./perf(+0x2a6119) [0x559222a94119]
./perf(+0x2a6de7) [0x559222a94de7]
./perf(cmd_test+0x25f) [0x559222a95686]
./perf(+0x2e4d25) [0x559222ad2d25]
./perf(+0x2e4faa) [0x559222ad2faa]
./perf(+0x2e50fd) [0x559222ad30fd]
./perf(main+0x29d) [0x559222ad3500]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf2) [0x7ff81df430b2]
test child interrupted
---- end ----
Simple expression parser: FAILED!
After the patch:
$ make DEBUG=1 NO_LIBBPF=1
$ ./perf test 7 -v
Couldn't bump rlimit(MEMLOCK), failures may take place when creating BPF maps, etc
7: Simple expression parser :
--- start ---
test child forked, pid 1960026
FAILED tests/expr.c:16 ids__new
FAILED tests/expr.c:16 ids__new
FAILED tests/expr.c:73 ids_union (-1 != 0)
test child finished with -1
---- end ----
Simple expression parser: FAILED!
so with the missing import fixex:
Tested-by: German Gomez <german.gomez@arm.com>
Reviewed-by: German Gomez <german.gomez@arm.com>
next prev parent reply other threads:[~2021-12-13 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 4:23 [PATCH] perf stat: Fix NULL vs IS_ERR() checking in check_per_pkg Miaoqian Lin
2021-12-12 14:55 ` German Gomez
2021-12-12 15:37 ` German Gomez
2021-12-13 7:09 ` [PATCH] perf expr: Fix return value of ids__new Miaoqian Lin
2021-12-13 13:13 ` German Gomez [this message]
2021-12-13 16:02 ` German Gomez
2021-12-13 13:57 ` German Gomez
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=d0fabb42-399f-2b72-412b-4f5ba6b9eea4@arm.com \
--to=german.gomez@arm.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linmq006@gmail.com \
--cc=linux-kernel@vger.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