[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180816154306.nllzlknw6n3we4pg@angband.pl>
Date: Thu, 16 Aug 2018 17:43:06 +0200
From: Adam Borowski <kilobyte@...band.pl>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Sven Joachim <svenjoac@....de>, 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 05:11:21PM +0200, Greg KH wrote:
> On Thu, Aug 16, 2018 at 03:59:58PM +0200, Sven Joachim wrote:
> > On 2018-08-16 15:05 +0200, Adam Borowski wrote:
> > > 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_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.
Probably obvious, but: cherry-picking that commit fixes the problem, it
builds, boots and works ok.
Thanks!
Meow.
--
⢀⣴⠾⠻⢶⣦⠀ What Would Jesus Do, MUD/MMORPG edition:
⣾⠁⢰⠒⠀⣿⡁ • multiplay with an admin char to benefit your mortal [Mt3:16-17]
⢿⡄⠘⠷⠚⠋⠀ • abuse item cloning bugs [Mt14:17-20, Mt15:34-37]
⠈⠳⣄⠀⠀⠀⠀ • use glitches to walk on water [Mt14:25-26]
Powered by blists - more mailing lists