From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752591AbdCPM3o (ORCPT ); Thu, 16 Mar 2017 08:29:44 -0400 Received: from mail.kernel.org ([198.145.29.136]:44774 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752555AbdCPM3Z (ORCPT ); Thu, 16 Mar 2017 08:29:25 -0400 Date: Thu, 16 Mar 2017 09:29:07 -0300 From: Arnaldo Carvalho de Melo To: Jiri Olsa , Josh Poimboeuf Cc: Arnd Bergmann , gregkh , "kernelci.org bot" , kernel-build-reports@lists.linaro.org, linux-mips@linux-mips.org, Linux Kernel Mailing List , stable@vger.kernel.org, Ralf Baechle , James Hogan , Ingo Molnar , Stephen Rothwell Subject: Re: stable build: 203 builds: 4 failed, 199 passed, 5 errors, 41 warnings (v4.10.1) Message-ID: <20170316122907.GS12825@kernel.org> References: <58b2dc6f.cf4d2e0a.f521.74b3@mx.google.com> <20170315072204.GB26837@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Wed, Mar 15, 2017 at 02:15:22PM +0100, Arnd Bergmann escreveu: > On Wed, Mar 15, 2017 at 8:22 AM, gregkh 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