linux-kernel - Re: stable build: 203 builds: 4 failed, 199 passed, 5 errors, 41 warnings (v4.10.1)

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: <CAK8P3a2hmA_f8YZKB=fqpcmeP0wRaq9aEORhVF1kLUWtd0nx6Q@mail.gmail.com>
Date:   Wed, 15 Mar 2017 14:15:22 +0100
From:   Arnd Bergmann <arnd@...db.de>
To:     gregkh <gregkh@...uxfoundation.org>
Cc:     "kernelci.org bot" <bot@...nelci.org>,
        kernel-build-reports@...ts.linaro.org, linux-mips@...ux-mips.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        stable@...r.kernel.org, Ralf Baechle <ralf@...ux-mips.org>,
        James Hogan <james.hogan@...tec.com>,
        Ingo Molnar <mingo@...hat.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: stable build: 203 builds: 4 failed, 199 passed, 5 errors, 41
 warnings (v4.10.1)

On Wed, Mar 15, 2017 at 8:22 AM, gregkh <gregkh@...uxfoundation.org> wrote:
>
> All now queued up in the stable trees, thanks.

Like 4.9.y it builds clean except for a couple of stack frame size warnings
and this one that continues to puzzle me.

/bin/sh: 1: /home/buildslave/workspace/kernel-builder/arch/x86/defconfig/allmodconfig+CONFIG_OF=n/label/builder/next/build-x86/tools/objtool//fixdep:
Permission denied

https://storage.kernelci.org/next/next-20170309/x86-allmodconfig+CONFIG_OF=n/build.log

The same warning is referenced in this email:
http://lkml.iu.edu/hypermail/linux/kernel/1612.0/04384.html

but I can't figure out what patch is supposed to address it, or if that
patch made it into mainline.

Curiously, only allmodconfig+CONFIG_OF=n seems to be broken, not
plain allmodconfig, maybe this could be related to rebuilding in the same
object tree without "make clean". Also, all recent kernels (since December)
until next-20170309 seem to be affected, but it does not show up on
the latest linux-next (next-20170310). I don't seen anything in next-20170310
that could have addressed it, so it may also be a coincidence that we don't
hit a certain race condition during build this time.

Adding Ingo, Arnaldo and Stephen to Cc, maybe they know what is going
on here.

      Arnd