linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Ian Rogers <irogers@google.com>,
	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@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Kan Liang <kan.liang@linux.intel.com>,
	Sandipan Das <sandipan.das@amd.com>,
	James Clark <james.clark@arm.com>,
	Dmitrii Dolgov <9erthalion6@gmail.com>,
	Changbin Du <changbin.du@huawei.com>,
	Rob Herring <robh@kernel.org>,
	Xing Zhengjun <zhengjun.xing@linux.intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] perf evsel: for_each_group fixes
Date: Tue, 23 May 2023 17:31:50 +0300	[thread overview]
Message-ID: <0a325fc8-2945-862a-e6bd-eb7b0ac46fe5@intel.com> (raw)
In-Reply-To: <20230523044446.1020769-2-irogers@google.com>

On 23/05/23 07:44, Ian Rogers wrote:
> Address/memory sanitizer was reporting issues in evsel__group_pmu_name
> because the for_each_group_evsel loop didn't terminate when the head
> was reached, the head would then be cast and accessed as an evsel
> leading to invalid memory accesses. Fix for_each_group_member and
> for_each_group_evsel to terminate at the list head. Note,
> evsel__group_pmu_name no longer iterates the group, but the problem is
> present regardless.
> 
> Fixes: 717e263fc354 ("perf report: Show group description when event group is enabled")
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
>  tools/perf/util/evsel.h         | 24 ++++++++++++++++--------
>  tools/perf/util/evsel_fprintf.c |  1 +
>  2 files changed, 17 insertions(+), 8 deletions(-)
> 
> diff --git a/tools/perf/util/evsel.h b/tools/perf/util/evsel.h
> index 820771a649b2..6a64543c7612 100644
> --- a/tools/perf/util/evsel.h
> +++ b/tools/perf/util/evsel.h
> @@ -462,16 +462,24 @@ static inline int evsel__group_idx(struct evsel *evsel)
>  }
>  
>  /* Iterates group WITHOUT the leader. */
> -#define for_each_group_member(_evsel, _leader) 					\
> -for ((_evsel) = list_entry((_leader)->core.node.next, struct evsel, core.node); \
> -     (_evsel) && (_evsel)->core.leader == (&_leader->core);					\
> -     (_evsel) = list_entry((_evsel)->core.node.next, struct evsel, core.node))
> +#define for_each_group_member_head(_evsel, _leader, _head)				\
> +for ((_evsel) = list_entry((_leader)->core.node.next, struct evsel, core.node);		\
> +	(_evsel) && (&(_evsel)->core.node != (_head)) &&				\

Extra parentheses perhaps not needed e.g. just

	&(_evsel)->core.node != (_head)

> +	(_evsel)->core.leader == (&_leader->core);					\

Parentheses look odd, maybe should be:

	&(_leader)->core

> +	(_evsel) = list_entry((_evsel)->core.node.next, struct evsel, core.node))
> +
> +#define for_each_group_member(_evsel, _leader)				\
> +	for_each_group_member_head(_evsel, _leader, &(_leader)->evlist->core.entries)

Did you consider using (_leader)->core.nr_members so that it is not
necessary to assume the evlist back pointer is populated.

>  
>  /* Iterates group WITH the leader. */
> -#define for_each_group_evsel(_evsel, _leader) 					\
> -for ((_evsel) = _leader; 							\
> -     (_evsel) && (_evsel)->core.leader == (&_leader->core);					\
> -     (_evsel) = list_entry((_evsel)->core.node.next, struct evsel, core.node))
> +#define for_each_group_evsel_head(_evsel, _leader, _head)				\
> +for ((_evsel) = _leader;								\
> +	(_evsel) && (&(_evsel)->core.node != (_head)) &&				\
> +	(_evsel)->core.leader == (&_leader->core);					\
> +	(_evsel) = list_entry((_evsel)->core.node.next, struct evsel, core.node))
> +
> +#define for_each_group_evsel(_evsel, _leader)				\
> +	for_each_group_evsel_head(_evsel, _leader, &(_leader)->evlist->core.entries)
>  
>  static inline bool evsel__has_branch_callstack(const struct evsel *evsel)
>  {
> diff --git a/tools/perf/util/evsel_fprintf.c b/tools/perf/util/evsel_fprintf.c
> index cc80ec554c0a..036a2171dc1c 100644
> --- a/tools/perf/util/evsel_fprintf.c
> +++ b/tools/perf/util/evsel_fprintf.c
> @@ -2,6 +2,7 @@
>  #include <inttypes.h>
>  #include <stdio.h>
>  #include <stdbool.h>
> +#include "util/evlist.h"
>  #include "evsel.h"
>  #include "util/evsel_fprintf.h"
>  #include "util/event.h"


  reply	other threads:[~2023-05-23 14:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23  4:44 [PATCH v1 1/2] perf evsel: evsel__group_pmu_name fixes Ian Rogers
2023-05-23  4:44 ` [PATCH v1 2/2] perf evsel: for_each_group fixes Ian Rogers
2023-05-23 14:31   ` Adrian Hunter [this message]
2023-05-23 17:04     ` Ian Rogers
2023-05-23 13:00 ` [PATCH v1 1/2] perf evsel: evsel__group_pmu_name fixes Adrian Hunter
2023-05-23 16:58   ` Ian Rogers
2023-05-29 16:03     ` Adrian Hunter
2023-05-29 16:16       ` 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=0a325fc8-2945-862a-e6bd-eb7b0ac46fe5@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=9erthalion6@gmail.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=changbin.du@huawei.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.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=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=robh@kernel.org \
    --cc=sandipan.das@amd.com \
    --cc=zhengjun.xing@linux.intel.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 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).