linux-kernel - Re: linux-next: build warning after merge of the wireless-drivers 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] [day] [month] [year] [list]

Date:   Fri, 16 Jun 2017 08:07:21 +0300
From:   Kalle Valo <kvalo@...eaurora.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Wireless <linux-wireless@...r.kernel.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Arend Van Spriel <arend.vanspriel@...adcom.com>
Subject: Re: linux-next: build warning after merge of the wireless-drivers tree

Stephen Rothwell <sfr@...b.auug.org.au> writes:

> After merging the wireless-drivers tree, today's linux-next build
> (x86_64 allmodconfig) produced this warning:
>
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c: In function
> 'brcmf_usb_probe_phase2':
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c:1198:2:
> warning: 'devinfo' may be used uninitialized in this function
> [-Wmaybe-uninitialized]
>   mutex_unlock(&devinfo->dev_init_lock);
>   ^
>
> Introduced by commit
>
>   6d0507a777fb ("brcmfmac: add parameter to pass error code in firmware callback")

Thanks, for the report. I also noticed this, only after I had applied
the patch, but hopefully Arend sends a patch to fix this soon.

-- 
Kalle Valo