From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@suse.de>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched/vtime: Fix an unitialized variable warning
Date: Mon, 30 Mar 2020 16:35:40 +0200 [thread overview]
Message-ID: <20200330143540.GQ20696@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200327214334.GF8015@zn.tnic>
On Fri, Mar 27, 2020 at 10:43:34PM +0100, Borislav Petkov wrote:
> Hi dude,
>
> right before I was going to send the trivial, shut-up-gcc variant, I
> thought that maybe we should do this instead.
>
> Thoughts?
>
> ---
> Fix:
>
> kernel/sched/cputime.c: In function ‘kcpustat_field’:
> kernel/sched/cputime.c:1007:6: warning: ‘val’ may be used \
> uninitialized in this function [-Wmaybe-uninitialized]
> 1007 | u64 val;
> | ^~~
>
> because gcc can't see that val is used only when err is 0.
>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> ---
> kernel/sched/cputime.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/sched/cputime.c b/kernel/sched/cputime.c
> index dac9104d126f..ff9435dee1df 100644
> --- a/kernel/sched/cputime.c
> +++ b/kernel/sched/cputime.c
> @@ -1003,12 +1003,12 @@ u64 kcpustat_field(struct kernel_cpustat *kcpustat,
> enum cpu_usage_stat usage, int cpu)
> {
> u64 *cpustat = kcpustat->cpustat;
> + u64 val = cpustat[usage];
> struct rq *rq;
> - u64 val;
> int err;
>
> if (!vtime_accounting_enabled_cpu(cpu))
> - return cpustat[usage];
> + return val;
>
> rq = cpu_rq(cpu);
Hurph.. this might result in an unconditional load (and extra
cache-miss) for the vtime_accounting_enabled_cpu() case.
I suspesct the =0 this would be better. Stupid stupid compiler!
next prev parent reply other threads:[~2020-03-30 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 21:43 [PATCH] sched/vtime: Fix an unitialized variable warning Borislav Petkov
2020-03-30 14:35 ` Peter Zijlstra [this message]
2020-04-15 9:14 ` [tip: sched/urgent] sched/vtime: Work around " tip-bot2 for Borislav Petkov
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=20200330143540.GQ20696@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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