From: Greg KH <gregkh@linuxfoundation.org>
To: Sven Joachim <svenjoac@gmx.de>
Cc: Adam Borowski <kilobyte@angband.pl>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
stable@vger.kernel.org, x86@kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Jiri Kosina <jkosina@suse.cz>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Linux 4.18.1
Date: Thu, 16 Aug 2018 17:11:21 +0200 [thread overview]
Message-ID: <20180816151121.GB10648@kroah.com> (raw)
In-Reply-To: <878t56mmxt.fsf@turtle.gmx.de>
On Thu, Aug 16, 2018 at 03:59:58PM +0200, Sven Joachim wrote:
> On 2018-08-16 15:05 +0200, Adam Borowski wrote:
>
> > On Thu, Aug 16, 2018 at 12:14:29PM +0200, Greg KH wrote:
> >> I'm announcing the release of the 4.18.1 kernel.
> >
> > I'm afraid that I get a build failure; v4.18 is ok, v4.18.1 fails with:
> >
> > ld: arch/x86/kvm/x86.o: in function `kvm_get_arch_capabilities':
> > (.text+0x43b2): undefined reference to `l1tf_vmx_mitigation'
>
> Same here and also in 4.17.15, but not in Linus' tree.
>
> > .config attached.
>
> Probably relevant:
>
> > CONFIG_KVM=y
> > # CONFIG_KVM_INTEL is not set
> > CONFIG_KVM_AMD=y
>
> I have CONFIG_KVM{,AMD}=m and CONFIG_KVM_INTEL is not set either.
This is fixed in my queue, if it really bothers you, apply commit
1eb46908b35d ("x86/l1tf: Fix build error seen if CONFIG_KVM_INTEL is
disabled") to your tree, it will be in the next round of stable kernel
releases.
thanks,
greg k-h
next prev parent reply other threads:[~2018-08-16 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 10:14 Linux 4.18.1 Greg KH
2018-08-16 10:14 ` Greg KH
2018-08-16 13:05 ` Adam Borowski
2018-08-16 13:59 ` Sven Joachim
2018-08-16 15:11 ` Greg KH [this message]
2018-08-16 15:43 ` Adam Borowski
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=20180816151121.GB10648@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=kilobyte@angband.pl \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=svenjoac@gmx.de \
--cc=tglx@linutronix.de \
--cc=x86@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