All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Thomas Richter <tmricht@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	svens@linux.ibm.com, gor@linux.ibm.com, sumanthk@linux.ibm.com,
	hca@linux.ibm.com
Subject: Re: [PATCH] tool/perf: Perf build fails on 5.12.0rc2 on s390
Date: Tue, 9 Mar 2021 09:43:34 -0300	[thread overview]
Message-ID: <YEdtdrb5GOaDIUlt@kernel.org> (raw)
In-Reply-To: <20210309110447.834292-1-tmricht@linux.ibm.com>

Em Tue, Mar 09, 2021 at 12:04:47PM +0100, Thomas Richter escreveu:
> perf build fails on 5.12.0rc2 on s390 with this error message:
> 
> util/synthetic-events.c: In function
> 				‘__event__synthesize_thread.part.0.isra’:
> util/synthetic-events.c:787:19: error: ‘kernel_thread’ may be
>     used uninitialized in this function [-Werror=maybe-uninitialized]
>     787 |   if (_pid == pid && !kernel_thread) {
>         |       ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~
> 
> The build succeeds using command 'make DEBUG=y'.
> 
> The variable kernel_thread is set by this function sequence:
> 
> __event__synthesize_thread()
> |    defines bool kernel_thread; as local variable and calls
> +--> perf_event__prepare_comm(..., &kernel_thread)
>      +--> perf_event__get_comm_ids(..., bool *kernel);
>           On return of this function variable kernel is always
>           set to true of false.

    s/of/or/

But it is only called for the host 'struct machine', if that is not the
case, then the value of 'kernel_thread' is left undefined/uninitialized,
right?

> 
> To prevent this compile error, assign variable kernel_thread
> a value when it is defined.

Applied, and added:

Fixes: c1b907953b2cd9ff ("perf tools: Skip PERF_RECORD_MMAP event synthesis for kernel threads")

Changed the subject to:

perf synthetic-events: Fix uninitialized 'kernel_thread' variable

As this doesn't affect just s/390, it is entirely possible that that
variable gets used with an undefined value.

- Arnaldo
 
> Output after:
> [root@m35lp76 perf]# make  util/synthetic-events.o
> ....
>  CC       util/synthetic-events.o
> [root@m35lp76 perf]#
> 
> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> ---
>  tools/perf/util/synthetic-events.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/perf/util/synthetic-events.c b/tools/perf/util/synthetic-events.c
> index b698046ec2db..5dd451695f33 100644
> --- a/tools/perf/util/synthetic-events.c
> +++ b/tools/perf/util/synthetic-events.c
> @@ -758,7 +758,7 @@ static int __event__synthesize_thread(union perf_event *comm_event,
>  	for (i = 0; i < n; i++) {
>  		char *end;
>  		pid_t _pid;
> -		bool kernel_thread;
> +		bool kernel_thread = false;
>  
>  		_pid = strtol(dirent[i]->d_name, &end, 10);
>  		if (*end)
> -- 
> 2.29.2
> 

-- 

- Arnaldo

      reply	other threads:[~2021-03-09 12:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 11:04 [PATCH] tool/perf: Perf build fails on 5.12.0rc2 on s390 Thomas Richter
2021-03-09 12:43 ` 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=YEdtdrb5GOaDIUlt@kernel.org \
    --to=acme@kernel.org \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sumanthk@linux.ibm.com \
    --cc=svens@linux.ibm.com \
    --cc=tmricht@linux.ibm.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.