From: gregkh <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: stable <stable@vger.kernel.org>, Olof Johansson <olof@lixom.net>,
Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>,
Olof's autobuilder <build@lixom.net>,
Sasha Levin <alexander.levin@verizon.com>
Subject: Re: stable-rc build: 20680 warnings 0 failures (stable-rc/v3.18.91-47-g4dc79b5)
Date: Wed, 17 Jan 2018 11:00:23 +0100 [thread overview]
Message-ID: <20180117100023.GA8954@kroah.com> (raw)
In-Reply-To: <CAK8P3a2tbu6UoME51KYLve1hF-F6rxUk7S15PbHvCJjHJ6Jf4g@mail.gmail.com>
On Tue, Jan 16, 2018 at 12:47:56PM +0100, Arnd Bergmann wrote:
> On Mon, Jan 15, 2018 at 2:30 PM, Olof's autobuilder <build@lixom.net> wrote:
> > Here are the build results from automated periodic testing.
> >
> > The tree being built was stable-rc, found at:
> >
> > URL: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> >
> > Branch: linux-3.18.y
> >
> > Topmost commits:
> > 4dc79b5 Linux 3.18.92-rc1
> > 00d0655 e1000e: Fix e1000_check_for_copper_link_ich8lan return value.
> > b944e64 uas: ignore UAS for Norelsys NS1068(X) chips
> >
> > Runtime: 28m 37s
> >
> > Passed: 131
> >
> > Warnings: 20680
> >
>
> > No errors
> >
> >
> > Warnings:
> >
> > arm64.allmodconfig:
> > /tmp/ccmFH2sM.s:77: Warning: ignoring incorrect section type for .init_array.00100
> > /tmp/ccmFH2sM.s:90: Warning: ignoring incorrect section type for .fini_array.00100
> > /tmp/ccCNAAf2.s:50: Warning: ignoring incorrect section type for .init_array.00100
> > /tmp/ccCNAAf2.s:63: Warning: ignoring incorrect section type for .fini_array.00100
> > /tmp/cckbGzsX.s:337: Warning: ignoring incorrect section type for .init_array.00100
> > /tmp/cckbGzsX.s:350: Warning: ignoring incorrect section type for .fini_array.00100
>
> This is the result of a bug in the assembler that has since been
> fixed. The warning
> itself is apparently harmless, but it's annoying to get 20000 lines of
> warnings for
> a simple allmodconfig build. I would suggest backporting commit
>
> cc622420798c ("gcov: disable for COMPILE_TEST")
>
> to all stable kernels 3.18, 4.1 and 4.4 that are affected by this.
> Olof's build bot
> only reported it for 3.18, but my interpretation is that he uses an
> older toolchain
> for that kernel, which triggers this warning, while newer assemblers are fixed.
>
> The warning showed up in the past few days after Olof's build scripts
> got adapted
> to also report assembler warnings, rather than just compiler warnings.
>
> The intention of the cc622420798c commit was to help with other issues of
> compile testing, fixing this particular warning was an unintended side-effect.
> Adding it to stable kernels will also help with the other issues it addressed at
> the time, in particular CPU usage during 'allmodconfig' build testing.
Good idea, I had to turn that off in my local build configs by hand,
this is much nicer :)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2018-01-17 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a5cad00.07b5620a.a2e2.b586@mx.google.com>
2018-01-16 11:47 ` stable-rc build: 20680 warnings 0 failures (stable-rc/v3.18.91-47-g4dc79b5) Arnd Bergmann
2018-01-17 10:00 ` gregkh [this message]
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=20180117100023.GA8954@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@verizon.com \
--cc=arnd@arndb.de \
--cc=build@lixom.net \
--cc=kernel-build-reports@lists.linaro.org \
--cc=olof@lixom.net \
--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.