From: Namhyung Kim <namhyung@kernel.org>
To: James Clark <james.clark@linaro.org>
Cc: linux-perf-users@vger.kernel.org, acme@kernel.org,
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>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Leo Yan <leo.yan@arm.com>, Dima Kogan <dima@secretsauce.net>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf probe: Fix uninitialized variable
Date: Mon, 9 Dec 2024 15:10:54 -0800 [thread overview]
Message-ID: <Z1d4_kq5WoFA1GsJ@google.com> (raw)
In-Reply-To: <20241209171222.1422577-1-james.clark@linaro.org>
On Mon, Dec 09, 2024 at 05:12:21PM +0000, James Clark wrote:
> Since the linked fixes: commit, err is returned uninitialized due to the
> removal of "return 0". Initialize err to fix it, and rename err to out
> to avoid confusion because buf is still supposed to be freed in non
> error cases.
>
> This fixes the following intermittent test failure on release builds:
>
> $ perf test "testsuite_probe"
> ...
> -- [ FAIL ] -- perf_probe :: test_invalid_options :: mutually exclusive options :: -L foo -V bar (output regexp parsing)
> Regexp not found: \"Error: switch .+ cannot be used with switch .+\"
> ...
Tested-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
>
> Fixes: 080e47b2a237 ("perf probe: Introduce quotation marks support")
> Signed-off-by: James Clark <james.clark@linaro.org>
> ---
> tools/perf/util/probe-event.c | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
> index 6d51a4c98ad7..35af6570cf9b 100644
> --- a/tools/perf/util/probe-event.c
> +++ b/tools/perf/util/probe-event.c
> @@ -1370,7 +1370,7 @@ int parse_line_range_desc(const char *arg, struct line_range *lr)
> {
> char *buf = strdup(arg);
> char *p;
> - int err;
> + int err = 0;
>
> if (!buf)
> return -ENOMEM;
> @@ -1383,20 +1383,20 @@ int parse_line_range_desc(const char *arg, struct line_range *lr)
> if (p == buf) {
> semantic_error("No file/function name in '%s'.\n", p);
> err = -EINVAL;
> - goto err;
> + goto out;
> }
> *(p++) = '\0';
>
> err = parse_line_num(&p, &lr->start, "start line");
> if (err)
> - goto err;
> + goto out;
>
> if (*p == '+' || *p == '-') {
> const char c = *(p++);
>
> err = parse_line_num(&p, &lr->end, "end line");
> if (err)
> - goto err;
> + goto out;
>
> if (c == '+') {
> lr->end += lr->start;
> @@ -1416,11 +1416,11 @@ int parse_line_range_desc(const char *arg, struct line_range *lr)
> if (lr->start > lr->end) {
> semantic_error("Start line must be smaller"
> " than end line.\n");
> - goto err;
> + goto out;
> }
> if (*p != '\0') {
> semantic_error("Tailing with invalid str '%s'.\n", p);
> - goto err;
> + goto out;
> }
> }
>
> @@ -1431,7 +1431,7 @@ int parse_line_range_desc(const char *arg, struct line_range *lr)
> lr->file = strdup_esq(p);
> if (lr->file == NULL) {
> err = -ENOMEM;
> - goto err;
> + goto out;
> }
> }
> if (*buf != '\0')
> @@ -1439,7 +1439,7 @@ int parse_line_range_desc(const char *arg, struct line_range *lr)
> if (!lr->function && !lr->file) {
> semantic_error("Only '@*' is not allowed.\n");
> err = -EINVAL;
> - goto err;
> + goto out;
> }
> } else if (strpbrk_esq(buf, "/."))
> lr->file = strdup_esq(buf);
> @@ -1448,10 +1448,10 @@ int parse_line_range_desc(const char *arg, struct line_range *lr)
> else { /* Invalid name */
> semantic_error("'%s' is not a valid function name.\n", buf);
> err = -EINVAL;
> - goto err;
> + goto out;
> }
>
> -err:
> +out:
> free(buf);
> return err;
> }
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-12-09 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 17:12 [PATCH] perf probe: Fix uninitialized variable James Clark
2024-12-09 23:10 ` Namhyung Kim [this message]
2024-12-10 13:26 ` Arnaldo Carvalho de Melo
2024-12-10 22:55 ` Masami Hiramatsu
[not found] ` <CA+JHD90Brn_jLxPPMr1M0RB6+ms1O3+OvOPWJ0wkUe+MXYpH1A@mail.gmail.com>
2024-12-11 8:39 ` James Clark
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=Z1d4_kq5WoFA1GsJ@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dima@secretsauce.net \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--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).