From: gregkh <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>,
Eduardo Valentin <eduval@amazon.com>,
Eduardo Valentin <edubezval@gmail.com>
Cc: "kernelci.org bot" <bot@kernelci.org>,
Tom Gall <tom.gall@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
Amit Pundir <amit.pundir@linaro.org>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
Anmar Oueja <anmar.oueja@linaro.org>,
stable <stable@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Kees Cook <keescook@chromium.org>, Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: stable-rc/linux-4.9.y build: 183 builds: 179 failed, 4 passed, 179 errors (v4.9.71-115-gd4b9c892aea4)
Date: Thu, 21 Dec 2017 15:49:20 +0100 [thread overview]
Message-ID: <20171221144920.GA28400@kroah.com> (raw)
In-Reply-To: <CAK8P3a34ufdWA2JwUjTFwh_w8g4TkwB+BrpMrgaFS-sOQL=EjA@mail.gmail.com>
On Thu, Dec 21, 2017 at 12:33:45PM +0100, Arnd Bergmann wrote:
> On Thu, Dec 21, 2017 at 12:06 PM, kernelci.org bot <bot@kernelci.org> wrote:
> > stable-rc/linux-4.9.y build: 183 builds: 179 failed, 4 passed, 179 errors (v4.9.71-115-gd4b9c892aea4)
> >
> > Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.9.y/kernel/v4.9.71-115-gd4b9c892aea4/
> >
> > Tree: stable-rc
> > Branch: linux-4.9.y
> > Git Describe: v4.9.71-115-gd4b9c892aea4
> > Git Commit: d4b9c892aea47e47ebc74e59533cef79f9ca30eb
> > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > Built: 4 unique architectures
> >
> > Build Failures Detected:
> >
> > arm64: gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05)
> >
> > allnoconfig: FAIL
> > defconfig: FAIL
> > tinyconfig: FAIL
> >
> > arm: gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05)
> >
> > acs5k_defconfig: FAIL
> > acs5k_tiny_defconfig: FAIL
> > allnoconfig: FAIL
>
> > Errors summary:
> >
> > 179 include/linux/sched.h:1479:35: error: field 'arch' has incomplete type
>
> This comes from 09b09ab71840 ("mm, x86/mm: Make the batched unmap TLB flush
> API more generic"), backported from e73ad5ff2f76d upstream.
>
> My 10-second analysis suggests that we should backport
> dcc2dc45f7cf ("sched/headers, mm: Move 'struct tlbflush_unmap_batch' from
> <linux/sched.h> to <linux/mm_types_task.h>")
Ugh, that's not a "straight" port at all, and will it really solve the
problem here? At first glance I don't see how, but I must be missing
something...
Eduardo, any ideas here? It's blowing up on your backported patch :(
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-21 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a3b95d2.8fd6500a.27126.ead9@mx.google.com>
2017-12-21 11:33 ` stable-rc/linux-4.9.y build: 183 builds: 179 failed, 4 passed, 179 errors (v4.9.71-115-gd4b9c892aea4) Arnd Bergmann
2017-12-21 14:49 ` gregkh [this message]
2017-12-21 18:19 ` Eduardo Valentin
2017-12-22 8:37 ` gregkh
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=20171221144920.GA28400@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amit.pundir@linaro.org \
--cc=anmar.oueja@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=arnd@arndb.de \
--cc=bot@kernelci.org \
--cc=edubezval@gmail.com \
--cc=eduval@amazon.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tom.gall@linaro.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).