From: Greg KH <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Build bot for Mark Brown <broonie@kernel.org>,
Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>,
linaro-kernel@lists.linaro.org,
"# 3.18.x" <stable@vger.kernel.org>,
Sasha Levin <alexander.levin@verizon.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: v3.18.86 build: 0 failures 1 warnings (v3.18.86)
Date: Wed, 3 Jan 2018 10:54:16 +0100 [thread overview]
Message-ID: <20180103095416.GD28246@kroah.com> (raw)
In-Reply-To: <CAK8P3a2exnZvbCT0K_KXL6-1FiEfPV9txM1tNDCNGcge=vZnSA@mail.gmail.com>
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
> <broonie@kernel.org> 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?
odd,
greg k-h
next prev parent reply other threads:[~2018-01-03 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 0:18 v3.18.86 build: 0 failures 1 warnings (v3.18.86) Build bot for Mark Brown
2018-01-02 23:24 ` Arnd Bergmann
2018-01-03 9:54 ` Greg KH [this message]
2018-01-03 9:57 ` Greg KH
2018-01-03 14:52 ` Arnd Bergmann
2018-01-03 14:59 ` Mark Brown
2018-01-03 15:32 ` Arnd Bergmann
2018-01-03 15:41 ` Mark Brown
2018-01-03 17:33 ` Greg KH
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=20180103095416.GD28246@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@verizon.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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).