public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf annotate-data: Fix a buffer overflow in TUI browser
Date: Mon, 12 Aug 2024 13:08:17 -0300	[thread overview]
Message-ID: <ZrozcZL1ganmoViy@x1> (raw)
In-Reply-To: <20240810191502.1947959-1-namhyung@kernel.org>

On Sat, Aug 10, 2024 at 12:15:02PM -0700, Namhyung Kim wrote:
> In get_member_overhead(), k is updated when it has a entry in the
> histogram.  But the entry->hists array is allocated with the number of
> evsel in the group.  So the k should be reset when it iterates the event
> using for_each_group_evsel(), otherwise it'd crash due to a buffer
> overflow.
> 
> Fixes: cb1898f58e0f ("perf annotate-data: Support --skip-empty option")

Thanks, applied to perf-tools-next,

- Arnaldo

> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
>  tools/perf/ui/browsers/annotate-data.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/perf/ui/browsers/annotate-data.c b/tools/perf/ui/browsers/annotate-data.c
> index c3db80a7589a..a937b55da736 100644
> --- a/tools/perf/ui/browsers/annotate-data.c
> +++ b/tools/perf/ui/browsers/annotate-data.c
> @@ -46,11 +46,12 @@ static int get_member_overhead(struct annotated_data_type *adt,
>  	struct annotated_member *member = entry->data;
>  	int i, k;
>  
> -	for (i = 0, k = 0; i < member->size; i++) {
> +	for (i = 0; i < member->size; i++) {
>  		struct type_hist *h;
>  		struct evsel *evsel;
>  		int offset = member->offset + i;
>  
> +		k = 0;
>  		for_each_group_evsel(evsel, leader) {
>  			if (symbol_conf.skip_empty &&
>  			    evsel__hists(evsel)->stats.nr_samples == 0)
> -- 
> 2.46.0.76.ge559c4bf1a-goog

      reply	other threads:[~2024-08-12 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+JHD90ZChq4FFyrqVYE9RvK=K2sKoD6T5dyYknK=STST9_AEQ@mail.gmail.com>
2024-08-10 19:15 ` [PATCH] perf annotate-data: Fix a buffer overflow in TUI browser Namhyung Kim
2024-08-12 16:08   ` 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=ZrozcZL1ganmoViy@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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