From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:40240 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751404AbeACJ5C (ORCPT ); Wed, 3 Jan 2018 04:57:02 -0500 Date: Wed, 3 Jan 2018 10:57:05 +0100 From: Greg KH To: Arnd Bergmann Cc: Build bot for Mark Brown , Kernel Build Reports Mailman List , linaro-kernel@lists.linaro.org, "# 3.18.x" , Sasha Levin , Linux Kernel Mailing List Subject: Re: v3.18.86 build: 0 failures 1 warnings (v3.18.86) Message-ID: <20180103095705.GA31335@kroah.com> References: <20180103095416.GD28246@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180103095416.GD28246@kroah.com> Sender: stable-owner@vger.kernel.org List-ID: On Wed, Jan 03, 2018 at 10:54:16AM +0100, Greg KH wrote: > On Wed, Jan 03, 2018 at 12:24:12AM +0100, Arnd Bergmann wrote: > > On Wed, Dec 6, 2017 at 1:18 AM, Build bot for Mark Brown > > wrote: > > > > > ------------------------------------------------------------------------------- > > > x86_64-defconfig : PASS, 0 errors, 2 warnings, 0 section mismatches > > > > > > Warnings: > > > ../include/linux/ftrace.h:632:36: warning: calling '__builtin_return_address' with a nonzero argument is unsafe [-Wframe-address] > > > ../include/linux/ftrace.h:632:36: warning: calling '__builtin_return_address' with a nonzero argument is unsafe [-Wframe-address] > > > ------------------------------------------------------------------------------- > > > > This warning keeps coming up in 3.18 and 4.1 builds, which lack a backport of > > > > ef6000b4c670 ("Disable the __builtin_return_address() warning globally > > after all") > > > > The other build bots use different gcc versions that don't report the > > warning here, > > so only Mark's bot triggers it. The warning in this file is harmless, > > and the patch > > only turns off the warning flag. > > Ah, I tried to figure this one out in the past, thanks for this, I'll > queue it up soon. Hm, this isn't in 4.4.y, why is it not showing up > there? Due to a different backport of this type of thing? Nope, doesn't apply to 3.18 at all, as the main part of this patch is already in there. I don't really understand it, it seems that the cc-disable-warning option isn't working for me for 3.18 at all in my local builds. I spent a few hours on it last week, but gave up in the end :( thanks, greg k-h