From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf test: Fix undefined behavior in bp_account
Date: Fri, 10 Jun 2022 15:41:08 -0300 [thread overview]
Message-ID: <YqOQRD62FIDNBkcH@kernel.org> (raw)
In-Reply-To: <20220610180247.444798-1-irogers@google.com>
Em Fri, Jun 10, 2022 at 11:02:47AM -0700, Ian Rogers escreveu:
> Fix:
> tests/bp_account.c:154:9: runtime error: variable length array bound evaluates to non-positive value 0
> by switching from a variable length to an allocated array.
Thanks, applied.
- Arnaldo
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/tests/bp_account.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/tests/bp_account.c b/tools/perf/tests/bp_account.c
> index d1ebb5561e5b..6f921db33cf9 100644
> --- a/tools/perf/tests/bp_account.c
> +++ b/tools/perf/tests/bp_account.c
> @@ -151,11 +151,21 @@ static int detect_ioctl(void)
> static int detect_share(int wp_cnt, int bp_cnt)
> {
> struct perf_event_attr attr;
> - int i, fd[wp_cnt + bp_cnt], ret;
> + int i, *fd = NULL, ret = -1;
> +
> + if (wp_cnt + bp_cnt == 0)
> + return 0;
> +
> + fd = malloc(sizeof(int) * (wp_cnt + bp_cnt));
> + if (!fd)
> + return -1;
>
> for (i = 0; i < wp_cnt; i++) {
> fd[i] = wp_event((void *)&the_var, &attr);
> - TEST_ASSERT_VAL("failed to create wp\n", fd[i] != -1);
> + if (fd[i] == -1) {
> + pr_err("failed to create wp\n");
> + goto out;
> + }
> }
>
> for (; i < (bp_cnt + wp_cnt); i++) {
> @@ -166,9 +176,11 @@ static int detect_share(int wp_cnt, int bp_cnt)
>
> ret = i != (bp_cnt + wp_cnt);
>
> +out:
> while (i--)
> close(fd[i]);
>
> + free(fd);
> return ret;
> }
>
> --
> 2.36.1.476.g0c4daa206d-goog
--
- Arnaldo
prev parent reply other threads:[~2022-06-10 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 18:02 [PATCH] perf test: Fix undefined behavior in bp_account Ian Rogers
2022-06-10 18:41 ` Arnaldo Carvalho de Melo [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=YqOQRD62FIDNBkcH@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--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