[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170316124958.GA3620@krava>
Date: Thu, 16 Mar 2017 13:49:58 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Jiri Olsa <jolsa@...nel.org>, Josh Poimboeuf <jpoimboe@...hat.com>,
Arnd Bergmann <arnd@...db.de>,
gregkh <gregkh@...uxfoundation.org>,
"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>,
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 Thu, Mar 16, 2017 at 09:29:07AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Mar 15, 2017 at 02:15:22PM +0100, Arnd Bergmann escreveu:
> > 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
>
> Jiri? Josh?
hum, looks like it imight be related to this fix we did for perf:
abb26210a395 perf tools: Force fixdep compilation at the start of the build
it's forcing fixdep to be build as first.. having it as a simple dependency
(which AFAICS is objtool case), the make -jX occasionaly raced on high cpu
servers, and executed unfinished binary, hence the permission fail
jirka
>
> - Arnaldo
>
> > 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
Powered by blists - more mailing lists