From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754228AbcESJHi (ORCPT ); Thu, 19 May 2016 05:07:38 -0400 Received: from mout.kundenserver.de ([212.227.126.187]:58982 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753818AbcESJHd (ORCPT ); Thu, 19 May 2016 05:07:33 -0400 From: Arnd Bergmann To: kernel-build-reports@lists.linaro.org Cc: "Olof's autobuilder" , olof@lixom.net, linuxppc-dev@lists.ozlabs.org, Michal Hocko , Andrew Morton , Linus Walleij , linux-kernel@vger.kernel.org, Stefano Stabellini , Ross Lagerwall , Dave Chinner , Krzysztof Kozlowski , Kishon Vijay Abraham I Subject: Re: next build: 37 warnings 2 failures (next/next-20160519) Date: Thu, 19 May 2016 11:07:09 +0200 Message-ID: <3211556.r7N0gQRgk6@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <573d6f0c.8664620a.24f8e.ffff931b@mx.google.com> References: <573d6f0c.8664620a.24f8e.ffff931b@mx.google.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:xa8s7wZ/l8Ym6W379l0ptetpLMMyFefLW1e5aYyylFMCt9oPlgS gzzFcK8guaBYzlj5XvMaQT1SZCl3fiBycJh9mtvQMgIVTA9INy0apTq0uu3RC8LmdaAKNd9 e6eUPcWEz1Ft0y5X9P7g2MI7NoEpXzor9H4GM5vRDZ90Zb/v+UZMyoZxQhQnNstNHgc3oqn ttFQj7RS0pJJHdjzP7mgw== X-UI-Out-Filterresults: notjunk:1;V01:K0:IpVbrAVE0BY=:lhbK/TtuxnYeQC4YjCQMbE Gm8pF9OxKVjYWUJeQ9CZbdjfsLe6fa8pBupEWH4RmmvKTwzRjdSb63WfE6tVQB3Y6O/thNNGI TtrqPAKIlmm8Pfmcwno68XrFtTPcEiUJ+3KFB0ZMrPHqbY1VUQlBWlcV/l0H0yO9rcwyScoRI ykbKcfsjpCgXCWEpgm9E6jKgPlVBkyMeTgdKeZUHjAiVjzeFxgiSYh04666N1HVYmZpTHgRqT YoBW302wNX0HmTf/ZAIEDA4K2+V6+qJm9jSow6Ze/5u7qnzXuclHDeeM1wQu6OHbHDNa2XvjB lAKF1k4C0E76pqjzvzsjc06b+5YwS2mAIaK9Z7muREzjq2MNp07abr9WE/TJEVblFUbLH0cay 12TPugzrPzCsfAENZ9GZVb43gMmgR6G1TNC08yzpiwqMQG8A6vL4/GdILQb9YRO1ZMp4k1795 zaLuWq4G/wDiO2B8/Qfe6Ffh4AgQFUBR2Z4HlmwQFzvx5bqOk1V75qTS39pTN+n9VLnJLr52r DiLn7vlFVcpmzHRrO3vImOXISar7CfgQ9jI3w7MTwStiy0t/0RE0HqayKeGnz1WuhOF9rIHOT vs6fbjkDYmK2J3xRyPIXvvJcjnfkSD+bEpIK/VDdLO5OtDAE/nXlhcJwRPnitJiox9bmY9eFu fWnE9KVD4zZLJMLf/bhYEEisZ81tQPPWXCywJOOxc9LXamaXCcdZkBI/zdDx9yX6r7hbU09Ya e7HahV6P8138PXLt Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 19 May 2016 00:45:16 Olof's autobuilder wrote: > Errors: > > arm64.allmodconfig: > samples/seccomp/bpf-fancy.c:13:27: fatal error: linux/seccomp.h: No such file or directory > samples/seccomp/dropper.c:20:27: fatal error: linux/seccomp.h: No such file or directory > samples/seccomp/bpf-helper.h:20:50: fatal error: linux/seccomp.h: No such file or directory > samples/seccomp/bpf-direct.c:21:27: fatal error: linux/seccomp.h: No such file or directory This one is interesting: the same header dependency seems to be present for samples/bpf, but only samples/seccomp fails. Can you check if both are attempted to be built? samples/bpf/README.rst says about this: |Kernel headers |-------------- | |There are usually dependencies to header files of the current kernel. |To avoid installing devel kernel headers system wide, as a normal |user, simply call:: | | make headers_install | |This will creates a local "usr/include" directory in the git/build top |level directory, that the make system automatically pickup first. which I assume would fix the problem, but it would be better if Kbuild was smart enough to do this implicitly when building these samples. > powerpc.pasemi_defconfig: > arch/powerpc/kernel/ptrace.c:380:24: error: index 32 denotes an offset greater than size of 'u64[32][1] {aka long long unsigned int[32][1]}' [-Werror=array-bounds] > arch/powerpc/kernel/ptrace.c:408:24: error: index 32 denotes an offset greater than size of 'u64[32][1] {aka long long unsigned int[32][1]}' [-Werror=array-bounds] I don't see a good way to avoid the warning other than dropping the BUILD_BUG_ON(offsetof(struct thread_fp_state, fpscr) != offsetof(struct thread_fp_state, fpr[32][0])); statements in the powerpc ptrace implementation. It doesn't seem too important to check for though. > Warnings: > 2 drivers/net/wireless/intel/iwlegacy/3945.c:1022:5: warning: suggest explicit braces to avoid ambiguous 'else' [-Wparentheses] I had not seen this before, sent a patch now. > 3 drivers/pinctrl/stm32/pinctrl-stm32.c:797:17: warning: too many arguments for format [-Wformat-extra-args] sent a fix yesterday, got an ack but it wasn't applied yet. I'm sure Linus Walleij will take care of it soon. > 6 mm/page_alloc.c:3651:6: warning: 'compact_result' may be used uninitialized in this function [-Wmaybe-uninitialized] I'm surprised this one is still there, I sent a patch but Michal Hocko came up with a better fix on May 12, which was not applied yet. Michael, can you resend this one to Andrew? I suspect he missed it as it was sent as a reply to mine. > 2 drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function] I sent a patch on May 11, subject "xen: remove incorrect forward declaration" and Stefano Stabellini reviewed it. Ross Lagerwall did the same patch a day earlier, but neither of them has made it into linux-next so far. According to Ross, this one should be backported to v4.4. > 3 fs/xfs/xfs_aops.c:97:16: warning: unused variable 'blockmask' [-Wunused-variable] I sent a patch on April 16, but got no reply. Resending it now. > 2 arch/arm/mach-lpc32xx/include/mach/irqs.h:115:0: warning: "NR_IRQS" redefined I missed this one, as I have some other patches for lp32xx in my randconfig fixup tree that hides it. I've created a fix now and applied it to the arm-soc fixes branch. > 1 drivers/soc/mediatek/mtk-pmic-wrap.c:1062:16: warning: large integer implicitly truncated to unsigned type [-Woverflow] > 1 drivers/soc/mediatek/mtk-pmic-wrap.c:1074:16: warning: large integer implicitly truncated to unsigned type [-Woverflow] > 1 drivers/soc/mediatek/mtk-pmic-wrap.c:1086:16: warning: large integer implicitly truncated to unsigned type [-Woverflow] I sent out a patch on May 12 for this, got no reply. I've applied my own patch now on the arm-soc fixes branch. > 1 drivers/phy/phy-exynos-mipi-video.c:238:13: warning: 'val' may be used uninitialized in this function [-Wmaybe-uninitialized] I sent a patch on May 11, it was reviewed by Krzysztof Kozlowski, but not yet applied. > 1 include/soc/nps/common.h:148:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] > 1 include/soc/nps/common.h:162:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] I sent a patch on May 12, but it hasn't appeared in linux-next yet. > 1 drivers/infiniband/core/cma.c:1253:12: warning: 'src_addr_storage.sin_addr.s_addr' may be used uninitialized in this function [-Wmaybe-uninitialized] This seems to only happen on powerpc. What compiler version are you using there? If it's an older compiler, we might not necessarily care about the warnings but you may want to upgrade. I've confirmed that this is a false positive, but I see how older gcc versions would get confused about this. > 1 include/sound/control.h:219:9: warning: 'master_vol' may be used uninitialized in this function [-Wmaybe-uninitialized] > sound/ppc/awacs.c:886:23: note: 'master_vol' was declared here > struct snd_kcontrol *master_vol, *speaker_vol; This seemed to be a valid bug at first sight, but it probably falls in the same category as the infiniband one, it's really a false positive. This is the Power Macintosh sound driver. > 7 include/linux/kernel.h:748:17: warning: comparison of distinct pointer types lacks a cast This is also powerpc specific it seems, the full message is /home/build/work/batch/mm/cma.c: In function 'cma_declare_contiguous': /home/build/work/batch/include/linux/kernel.h:748:17: warning: comparison of distinct pointer types lacks a cast (void) (&_max1 == &_max2); \ ^ /home/build/work/batch/include/linux/kernel.h:747:9: note: in definition of macro 'max' typeof(y) _max2 = (y); \ ^ /home/build/work/batch/mm/cma.c:270:29: note: in expansion of macro 'max' (phys_addr_t)PAGE_SIZE << max(MAX_ORDER - 1, pageblock_order)); ^~~ Probably straightforward to fix, but I haven't looked closely. > 1 drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] > 1 fs/gfs2/dir.c:1021:8: warning: 'leaf_no' may be used uninitialized in this function [-Wmaybe-uninitialized] > 1 fs/gfs2/dir.c:802:9: warning: 'leaf_no' may be used uninitialized in this function [-Wmaybe-uninitialized] > 1 fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized] These are all warnings that we only get for arm64, and I think they are all false positives on older gcc versions. Arnd