stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Jiri Olsa <jolsa@kernel.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	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 16:17:04 +0100	[thread overview]
Message-ID: <20170316151704.GA20999@krava> (raw)
In-Reply-To: <20170316150338.GV12825@kernel.org>

On Thu, Mar 16, 2017 at 12:03:38PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Mar 16, 2017 at 03:39:36PM +0100, Arnd Bergmann escreveu:
> > On Thu, Mar 16, 2017 at 2:59 PM, Jiri Olsa <jolsa@redhat.com> wrote:
> > > On Thu, Mar 16, 2017 at 02:44:45PM +0100, Arnd Bergmann wrote:
> > >> On Thu, Mar 16, 2017 at 1:49 PM, Jiri Olsa <jolsa@redhat.com> wrote:
> > >> > 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@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?
> > >> >
> > >> > 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
> > >>
> > >> It's probably another variation of this bug, but the commit you cite got merged
> > >> into 4.10-rc1, while the problem still persists in mainline (4.11-rc2+).
> > >
> > > the problem is in objtool build right? the fix was for perf build
> > 
> > Ah, got it. Yes, that must be it then. I supposed we coul duplicate what you
> > did for perf in objtool, but a cleaner way would be to generalize it for all of
> > tools/, right?

right, the thing is that objtool is standalone application like perf,
and before their builds can go the 'fixdep' needs to be there.. that's
a condition to use the tools/build framework

not sure how offensive it'd be to current Makefiles if we come with some
generalized code to do that.. I'll think about it, but I think we might
be better of the way we are now

> 
> Humm, can't we have just one fixdep?

we have.. it's just the matter who will build it first ;-)

jirka

  reply	other threads:[~2017-03-16 15:17 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
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 [this message]
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=20170316151704.GA20999@krava \
    --to=jolsa@redhat.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).