linux-kernel - Re: linux-next: build warning after merge of the qcom tree

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <154350904879.88331.1156146258217230705@swboyd.mtv.corp.google.com>
Date:   Thu, 29 Nov 2018 08:30:48 -0800
From:   Stephen Boyd <swboyd@...omium.org>
To:     Andy Gross <agross@...eaurora.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the qcom tree

Quoting Stephen Rothwell (2018-11-28 13:25:40)
> Hi all,
> 
> On Fri, 16 Nov 2018 10:10:59 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > Hi all,
> > 
> > After merging the qcom tree, today's linux-next build (arm
> > multi_v7_defconfig) produced this warning:
> > 
> > drivers/gpu/drm/msm/adreno/a6xx_gmu.c: In function 'a6xx_gmu_rpmh_arc_votes_init.constprop':
> > drivers/gpu/drm/msm/adreno/a6xx_gmu.c:943:12: warning: 'pri_count' is used uninitialized in this function [-Wuninitialized]
> >   pri_count >>= 1;
> >             ^~~
> > drivers/gpu/drm/msm/adreno/a6xx_gmu.c:948:12: warning: 'sec_count' may be used uninitialized in this function [-Wmaybe-uninitialized]
> >   sec_count >>= 1;
> >             ^~~
> > 
> > Introduced by commit
> > 
> >   ed3cafa79ea7 ("soc: qcom: cmd-db: Stop memcpy()ing in cmd_db_read_aux_data()")
> > 
> > # CONFIG_QCOM_COMMAND_DB is not set
> 
> I am still getting these warnings.
> 

Andy's email isn't at codeaurora.org anymore. Not sure if that matters
but he may be missing this.

Either way, thanks for the report. Fix coming shortly.