From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 136ECC43441 for ; Thu, 15 Nov 2018 00:27:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DB8F8208A3 for ; Thu, 15 Nov 2018 00:27:46 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DB8F8208A3 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727299AbeKOKdR (ORCPT ); Thu, 15 Nov 2018 05:33:17 -0500 Received: from mga05.intel.com ([192.55.52.43]:26296 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727128AbeKOKdR (ORCPT ); Thu, 15 Nov 2018 05:33:17 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Nov 2018 16:27:45 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,234,1539673200"; d="scan'208";a="86546176" Received: from tassilo.jf.intel.com (HELO tassilo.localdomain) ([10.7.201.126]) by fmsmga008.fm.intel.com with ESMTP; 14 Nov 2018 16:27:44 -0800 Received: by tassilo.localdomain (Postfix, from userid 1000) id AB3B3300E46; Wed, 14 Nov 2018 16:27:44 -0800 (PST) Date: Wed, 14 Nov 2018 16:27:44 -0800 From: Andi Kleen To: Michal Hocko Cc: Thomas Gleixner , Jiri Kosina , Linus Torvalds , Dave Hansen , Borislav Petkov , LKML , linux-mm@kvack.org, Michal Hocko Subject: Re: [PATCH] l1tf: drop the swap storage limit restriction when l1tf=off Message-ID: <20181115002744.GM6218@tassilo.jf.intel.com> References: <20181113184910.26697-1-mhocko@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181113184910.26697-1-mhocko@kernel.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 13, 2018 at 07:49:10PM +0100, Michal Hocko wrote: > From: Michal Hocko > > Swap storage is restricted to max_swapfile_size (~16TB on x86_64) > whenever the system is deemed affected by L1TF vulnerability. Even > though the limit is quite high for most deployments it seems to be > too restrictive for deployments which are willing to live with the > mitigation disabled. > > We have a customer to deploy 8x 6,4TB PCIe/NVMe SSD swap devices > which is clearly out of the limit. > > Drop the swap restriction when l1tf=off is specified. It also doesn't > make much sense to warn about too much memory for the l1tf mitigation > when it is forcefully disabled by the administrator. Reviewed-by: Andi Kleen -Andi