All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	Andi Kleen <ak@linux.intel.com>,
	linux-kernel@vger.kernel.org,
	Stephane Eranian <eranian@google.com>,
	Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH] perf llvm: don't access out-of-scope array
Date: Fri, 27 Sep 2019 12:26:51 -0300	[thread overview]
Message-ID: <20190927152651.GA20644@kernel.org> (raw)
In-Reply-To: <20190926220018.25402-1-irogers@google.com>

Em Thu, Sep 26, 2019 at 03:00:18PM -0700, Ian Rogers escreveu:
> test_dir is assigned to the release array which is out-of-scope 3 lines
> later. Extend the scope of the release array so that an out-of-scope
> array isn't accessed.
> Bug detected by clang's address sanitizer.

This one is really ironic, code to support using clang/llvm in perf is
caught with a bug detected by clang's utilities ;-)

Please next time try to use 'git blame' so as to add this:

[root@quaco perf]# git tag --contains 07bc5c699a3d | grep ^v[[:digit:]] | sort --version-sort | head -1
v4.4
[root@quaco perf]#

Cc: Wang Nan <wangnan0@huawei.com>
Cc: stable@vger.kernel.org # v4.4+
Fixes: 07bc5c699a3d ("perf tools: Make fetch_kernel_version() publicly available")

And help get noticed by the various backport bots out there.

Thanks a lot, applied!

- Arnaldo
 
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
>  tools/perf/util/llvm-utils.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/tools/perf/util/llvm-utils.c b/tools/perf/util/llvm-utils.c
> index 8d04e3d070b1..8b14e4a7f1dc 100644
> --- a/tools/perf/util/llvm-utils.c
> +++ b/tools/perf/util/llvm-utils.c
> @@ -233,14 +233,14 @@ static int detect_kbuild_dir(char **kbuild_dir)
>  	const char *prefix_dir = "";
>  	const char *suffix_dir = "";
>  
> +	/* _UTSNAME_LENGTH is 65 */
> +	char release[128];
> +
>  	char *autoconf_path;
>  
>  	int err;
>  
>  	if (!test_dir) {
> -		/* _UTSNAME_LENGTH is 65 */
> -		char release[128];
> -
>  		err = fetch_kernel_version(NULL, release,
>  					   sizeof(release));
>  		if (err)
> -- 
> 2.23.0.444.g18eeb5a265-goog

-- 

- Arnaldo

  reply	other threads:[~2019-09-27 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 22:00 [PATCH] perf llvm: don't access out-of-scope array Ian Rogers
2019-09-27 15:26 ` Arnaldo Carvalho de Melo [this message]
2019-10-07 14:49 ` [tip: perf/urgent] perf llvm: Don't " tip-bot2 for 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=20190927152651.GA20644@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=wangnan0@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.