linux-kernel - Re: master build: 0 failures 3 warnings (v4.7-rc3-87-gbb96727)

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

Date:	Fri, 17 Jun 2016 14:10:32 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	linaro-kernel@...ts.linaro.org
Cc:	Build bot for Mark Brown <broonie@...nel.org>,
	kernel-build-reports@...ts.linaro.org,
	linux-kernel@...r.kernel.org,
	Stefano Stabellini <sstabellini@...nel.org>,
	Jonathan Cameron <jic23@...nel.org>
Subject: Re: master build: 0 failures 3 warnings (v4.7-rc3-87-gbb96727)

On Friday, June 17, 2016 1:00:40 PM CEST Build bot for Mark Brown wrote:
>           2 ../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function]

-stable regression, still not fixed. Stefano applied the patch
into xen-tip/linux-next, but so far it has not shown up into v4.7,
so Greg hasn't had a chance to backport it.

>           1 ../fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized]

A patch is in linux-next now, my original patch was wrong, but the new
one should work. I suspect this will have to wait for v4.8 though,
as the current code is not broken and the warning has been around
for a long time.

>           1 ../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized]

Jonathan Cameron applied my patch to his "fixes-togreg" branch last Saturday,
but it hasn't shown up in linux-next or mainline yet.

	Arnd