From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@kernel.org>, Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
gregkh <gregkh@linuxfoundation.org>,
"kernelci.org bot" <bot@kernelci.org>,
kernel-build-reports@lists.linaro.org, linux-mips@linux-mips.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
James Hogan <james.hogan@imgtec.com>,
Ingo Molnar <mingo@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: stable build: 203 builds: 4 failed, 199 passed, 5 errors, 41 warnings (v4.10.1)
Date: Thu, 16 Mar 2017 09:29:07 -0300 [thread overview]
Message-ID: <20170316122907.GS12825@kernel.org> (raw)
In-Reply-To: <CAK8P3a2hmA_f8YZKB=fqpcmeP0wRaq9aEORhVF1kLUWtd0nx6Q@mail.gmail.com>
Em Wed, Mar 15, 2017 at 02:15:22PM +0100, Arnd Bergmann escreveu:
> On Wed, Mar 15, 2017 at 8:22 AM, gregkh <gregkh@linuxfoundation.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?
- 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
next prev parent reply other threads:[~2017-03-16 12:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58b2dc6f.cf4d2e0a.f521.74b3@mx.google.com>
2017-02-28 13:31 ` stable build: 203 builds: 4 failed, 199 passed, 5 errors, 41 warnings (v4.10.1) Arnd Bergmann
2017-03-15 7:22 ` gregkh
2017-03-15 13:15 ` Arnd Bergmann
2017-03-16 12:29 ` Arnaldo Carvalho de Melo [this message]
2017-03-16 12:49 ` Jiri Olsa
2017-03-16 13:44 ` Arnd Bergmann
2017-03-16 13:59 ` Jiri Olsa
2017-03-16 14:39 ` Arnd Bergmann
2017-03-16 15:03 ` Arnaldo Carvalho de Melo
2017-03-16 15:17 ` Jiri Olsa
2017-03-16 15:46 ` Arnaldo Carvalho de Melo
2017-03-16 15:50 ` Jiri Olsa
2017-03-16 16:44 ` Jiri Olsa
2017-03-16 17:03 ` Josh Poimboeuf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170316122907.GS12825@kernel.org \
--to=acme@kernel.org \
--cc=arnd@arndb.de \
--cc=bot@kernelci.org \
--cc=gregkh@linuxfoundation.org \
--cc=james.hogan@imgtec.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mingo@redhat.com \
--cc=ralf@linux-mips.org \
--cc=sfr@canb.auug.org.au \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.