[MODERATED] Re: L!TF Bulletin #4: The state of the horrors

[Greg KH <gregkh@linuxfoundation.org>]

On Sat, Jul 14, 2018 at 02:57:00PM +0200, speck for Thomas Gleixner wrote:
> On Fri, 13 Jul 2018, speck for Konrad Rzeszutek Wilk wrote:
> > On Fri, Jul 13, 2018 at 05:08:35PM +0200, speck for Thomas Gleixner wrote:
> > > Hi!
> > > 
> > > The repository has been updated with the following changes since bulletin #3:
> > > 
> > >   - Online sibling threads when SMT control is switched from off to on
> > > 
> > >   - Expose the VMX mitigation state properly in the l1tf vulnerability file
> > > 
> > >   - Fix EPT off handling
> > > 
> > >   - Make the kvm L1D flush parameter runtime controllable
> > > 
> > >   - Add the 'l1tf' kernel command line option
> > > 
> > >   - Add documentation about the whole mess
> > > 
> > > The master branch is still based on 4.18-rc1 and merges almost cleanly into
> > > 4.18-rc4+ with a very trivial conflict. It's not going to be rebased
> > > because the commit SHA1s are used in the stable branches and are also
> > > already used in distro backports.
> > > 
> > > The stable branches linux-4.14.y, linux-4.16.y and linux-4.17.y have been
> > > rebased to the latest stable versions. David Woodhouse said he's looking
> > > into updating the linux-4.9.y stable branch in the next days.
> > > 
> > > Git bundle against v4.18-rc1 is attached.
> > > 
> > > Thanks everyone involved for patches, testing, review and entertaining
> > > discussions!
> > 
> > You may also want to backport 
> > 
> > git cherry-pick 84676c1f21e8
> > git cherry-pick adbe552349f2d
> > 
> > As in the stable trees. The reason being that with 'nosmt' the megasas controller
> > goes bonky and stops working.
> 
> I'd prefer to route them directly to stable as the stuff is already broken
> with maxcpus=N. Greg?

Good idea, I'll queue these up directly, thanks.

greg k-h