From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: stable <stable@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
David Woodhouse <dwmw@amazon.co.uk>,
Thomas Gall <tom.gall@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
Anmar Oueja <anmar.oueja@linaro.org>
Subject: Re: stable-rc/linux-4.4.y build: 178 builds: 1 failed, 177 passed, 4 errors (v4.4.111-88-gaee64ffb2ece)
Date: Mon, 15 Jan 2018 14:46:08 +0100 [thread overview]
Message-ID: <20180115134608.GA31888@kroah.com> (raw)
In-Reply-To: <20180115124836.GA30325@kroah.com>
On Mon, Jan 15, 2018 at 01:48:36PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Jan 15, 2018 at 06:05:30PM +0530, Amit Pundir wrote:
> > Hi Greg,
> >
> > On 15 January 2018 at 17:21, kernelci.org bot <bot@kernelci.org> wrote:
> > > stable-rc/linux-4.4.y build: 178 builds: 1 failed, 177 passed, 4 errors (v4.4.111-88-gaee64ffb2ece)
> > >
> > > Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.111-88-gaee64ffb2ece/
> > >
> > > Tree: stable-rc
> > > Branch: linux-4.4.y
> > > Git Describe: v4.4.111-88-gaee64ffb2ece
> > > Git Commit: aee64ffb2ececdfe86f0a00fb46f28aaad5f3acd
> > > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > > Built: 4 unique architectures
> > >
> > > Build Failure Detected:
> > >
> > > x86: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
> > >
> > > i386_defconfig: FAIL
> > >
> > > Errors Detected:
> > >
> > > x86: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
> > >
> > > i386_defconfig: 4 errors
> > >
> > > Errors summary:
> > >
> > > 1 arch/x86/kernel/cpu/bugs.c:76:24: error: 'X86_BUG_SPECTRE_V2' undeclared (first use in this function)
> > > 1 arch/x86/kernel/cpu/bugs.c:68:24: error: 'X86_BUG_SPECTRE_V1' undeclared (first use in this function)
> > > 1 arch/x86/kernel/cpu/bugs.c:60:19: error: 'X86_FEATURE_PTI' undeclared (first use in this function)
> > > 1 arch/x86/kernel/cpu/bugs.c:58:24: error: 'X86_BUG_CPU_MELTDOWN' undeclared (first use in this function)
> > >
> > >
> >
> > Build failed due to following missing upstream patch backports for
> > linux-4.4.y. I don't see these patches in queue-4.4 either. I'm not
> > aware of other dependencies of these patches:
> >
> > a89f040fa34e ("x86/cpufeatures: Add X86_BUG_CPU_INSECURE")
> >
> > de791821c295c ("x86/pti: Rename BUG_CPU_INSECURE to BUG_CPU_MELTDOWN")
> >
> > 99c6fa2511d8 ("x86/cpufeatures: Add X86_BUG_SPECTRE_V[12]")
> >
> > Regards,
> > Amit Pundir
> >
> > <snip> ..
>
> Ah crap, I didn't catch this as I only built a x86-64 kernel here. You
> are right, let me go backport these as well...
Ok, should now be fixed, thanks for the report, you beat 0-day's
response :)
greg k-h
prev parent reply other threads:[~2018-01-15 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a5c95bf.81bedf0a.db07c.6e8b@mx.google.com>
2018-01-15 12:35 ` stable-rc/linux-4.4.y build: 178 builds: 1 failed, 177 passed, 4 errors (v4.4.111-88-gaee64ffb2ece) Amit Pundir
2018-01-15 12:48 ` Greg Kroah-Hartman
2018-01-15 13:46 ` Greg Kroah-Hartman [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=20180115134608.GA31888@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amit.pundir@linaro.org \
--cc=anmar.oueja@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=dwmw@amazon.co.uk \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tglx@linutronix.de \
--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 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.