[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180816151121.GB10648@kroah.com>
Date: Thu, 16 Aug 2018 17:11:21 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Sven Joachim <svenjoac@....de>
Cc: Adam Borowski <kilobyte@...band.pl>, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
stable@...r.kernel.org, x86@...nel.org, kvm@...r.kernel.org,
Paolo Bonzini <pbonzini@...hat.com>,
Jiri Kosina <jkosina@...e.cz>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Linux 4.18.1
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
Powered by blists - more mailing lists