Re: [PATCH] l1tf: drop the swap storage limit restriction when l1tf=off

From: Jiri Kosina <jikos@kernel.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Dave Hansen <dave.hansen@intel.com>,
	Andi Kleen <ak@linux.intel.com>, Borislav Petkov <bp@suse.de>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: [PATCH] l1tf: drop the swap storage limit restriction when l1tf=off
Date: Sun, 9 Dec 2018 21:46:57 +0100 (CET)	[thread overview]
Message-ID: <nycvar.YFH.7.76.1812092145510.17216@cbobk.fhfr.pm> (raw)
In-Reply-To: <20181119135149.GN22247@dhcp22.suse.cz>

On Mon, 19 Nov 2018, Michal Hocko wrote:

> > > > > +				It also drops the swap size and available
> > > > > +				RAM limit restriction.
> > > > 
> > > > Minor nit: I think this should explicitly mention that those two things 
> > > > are related to bare metal mitigation, to avoid any confusion (as otherwise 
> > > > the l1tf cmdline parameter is purely about hypervisor mitigations).
> > > 
> > > Do you have any specific wording in mind?
> > > 
> > > It also drops the swap size and available RAM limit restrictions on both
> > > hypervisor and bare metal.
> > > 
> > > Sounds better?
> > > 
> > > > With that
> > > > 
> > > > 	Acked-by: Jiri Kosina <jkosina@suse.cz>
> > > 
> > > Thanks!
> > 
> > Yes, I think that makes it absolutely clear. Thanks,
> 
> OK. Here is the incremental diff on top of the patch. I will fold and
> repost later this week. I assume people are still catching up after LPC
> and I do not want to spam them even more.

Is this queued anywhere in the meantime please?

Thanks,

-- 
Jiri Kosina
SUSE Labs