linux-kernel - Re: perf: bench/sched-messaging.c:73:13: error: 'dummy' may be used uninitialized

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <YPAWlsL4a5uqrDWU@kroah.com>
Date:   Thu, 15 Jul 2021 13:05:58 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Anders Roxell <anders.roxell@...aro.org>
Cc:     Naresh Kamboju <naresh.kamboju@...aro.org>,
        perf-users <perf-users@...aro.org>,
        open list <linux-kernel@...r.kernel.org>,
        linux-stable <stable@...r.kernel.org>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Ingo Molnar <mingo@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Sasha Levin <sashal@...nel.org>, Leo Yan <leo.yan@...aro.org>
Subject: Re: perf: bench/sched-messaging.c:73:13: error: 'dummy' may be used
 uninitialized

On Tue, Jul 13, 2021 at 05:32:17PM +0200, Anders Roxell wrote:
> On Tue, 13 Jul 2021 at 17:18, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >
> > On Tue, Jul 13, 2021 at 08:40:28PM +0530, Naresh Kamboju wrote:
> > > LKFT have noticed these warnings / errors when we have updated gcc version from
> > > gcc-9 to gcc-11 on stable-rc linux-5.4.y branch. I have provided the steps to
> > > reproduce in this email below.
> > >
> > > Following perf builds failed with gcc-11 with linux-5.4.y branch.
> > > - build-arm-gcc-11-perf
> > > - build-arm64-gcc-11-perf
> > > - build-i386-gcc-11-perf
> > > - build-x86-gcc-11-perf
> > >
> > > Build error log:
> > > --------------------
> >
> > <snip>
> >
> > I imagine this is fixed in newer kernel versions, so if you could
> > provide the git ids of the patches needed to fix this up in 5.4, that
> > would be great!
> 
> You were correct, I did a bisect [1] and found
> d493720581a6 ("perf bench: Fix 2 memory sanitizer warnings").
> 
> commit d2c73501a767514b6c85c7feff9457a165d51057 upstream.
> 
> Cherry picked it and I was able to build it on arm64 and x86.

Great, now queued up, thanks.

greg k-h