Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp7053imd; Fri, 2 Nov 2018 16:32:47 -0700 (PDT) X-Google-Smtp-Source: AJdET5cH9XjarG/f6yyHiRLBTMz4dR0u6sJouPqojao77BcTsoMskbswt8Btm9TT+UErau2ADPZS X-Received: by 2002:a63:61c8:: with SMTP id v191mr12666116pgb.242.1541201567921; Fri, 02 Nov 2018 16:32:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1541201567; cv=none; d=google.com; s=arc-20160816; b=0Y+lQkVFYD5wm5yh2oIb6a4FaXFAqTeEI5g4VTca3PrNjLLeArZikrse7MJga03mJP 8sisx9q6kqOSPl2D+IXQmo+aR/M8OfsDVjWGe3uldOoNHwYL7yH7NPb80GxL0641F4yO u7TeO8w5Jarh3MxfJPxNUekno5aE2MK+5s0+USXaOvzxzBM6faO5GHIzLdXeSL1E7HKs b/dkInzMtp+Aq2S04pHOm3YbJVI0dK+iXQ6zSSMRFzk9b5hPr4k5V6l6shavgcuBzOkB EqaEAAY64nVuc1V23OTZR4N2TJxVhoHjFuljjh2IwXxbv7ypVhWxHQZrxdH0JE6PUZIG QgvA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from; bh=8ZvhPmiEqzfBXCEdOzKlm4Q7YcX8ZtXObk52dex3Jm4=; b=j4AT0iRrvNdWoFUON7uGCBL8jBg9K8en4jLXuJttTQqJMaNqItJ4EZVf9xlW5qTGQh dUoU4MPGfHbZV1/Qnwzwwpxx3Iy6bxpdSxxwQoCxHWfT0J0jvD9n3O+8o3MqdZ6V4/C4 93U8KfZvogN3uNVUIJgBgKQeveRa/0Fwq2nrKeHnX7f+2P5DYRmnkxnmrzGmlY8wJCJi iMowq+v3UVynVtnqMMBB8s7XMxO9e7bmBRMWhofWEg3nOjnLllr73sE2ncKHKfbBLU+H AoEH084e0zF9blB1dWG6k7f3DQZODniaVPz6yCsAIiH/TpGXJS1GQ4fYroA5YrkqpDGD MdFw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=vmware.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r12-v6si34250139plo.269.2018.11.02.16.32.33; Fri, 02 Nov 2018 16:32:47 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=vmware.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728671AbeKCIlO (ORCPT + 99 others); Sat, 3 Nov 2018 04:41:14 -0400 Received: from ex13-edg-ou-001.vmware.com ([208.91.0.189]:8611 "EHLO EX13-EDG-OU-001.vmware.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728485AbeKCIk6 (ORCPT ); Sat, 3 Nov 2018 04:40:58 -0400 Received: from sc9-mailhost2.vmware.com (10.113.161.72) by EX13-EDG-OU-001.vmware.com (10.113.208.155) with Microsoft SMTP Server id 15.0.1156.6; Fri, 2 Nov 2018 16:31:32 -0700 Received: from sc2-haas01-esx0118.eng.vmware.com (sc2-haas01-esx0118.eng.vmware.com [10.172.44.118]) by sc9-mailhost2.vmware.com (Postfix) with ESMTP id A6A7FB14D2; Fri, 2 Nov 2018 19:31:42 -0400 (EDT) From: Nadav Amit To: Ingo Molnar CC: , , "H. Peter Anvin" , Thomas Gleixner , Borislav Petkov , Dave Hansen , Andy Lutomirski , Kees Cook , Peter Zijlstra , Dave Hansen , Nadav Amit Subject: [PATCH v3 3/7] x86/mm: temporary mm struct Date: Fri, 2 Nov 2018 16:29:42 -0700 Message-ID: <20181102232946.98461-4-namit@vmware.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20181102232946.98461-1-namit@vmware.com> References: <20181102232946.98461-1-namit@vmware.com> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: None (EX13-EDG-OU-001.vmware.com: namit@vmware.com does not designate permitted sender hosts) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Andy Lutomirski Sometimes we want to set a temporary page-table entries (PTEs) in one of the cores, without allowing other cores to use - even speculatively - these mappings. There are two benefits for doing so: (1) Security: if sensitive PTEs are set, temporary mm prevents their use in other cores. This hardens the security as it prevents exploding a dangling pointer to overwrite sensitive data using the sensitive PTE. (2) Avoiding TLB shootdowns: the PTEs do not need to be flushed in remote page-tables. To do so a temporary mm_struct can be used. Mappings which are private for this mm can be set in the userspace part of the address-space. During the whole time in which the temporary mm is loaded, interrupts must be disabled. The first use-case for temporary PTEs, which will follow, is for poking the kernel text. [ Commit message was written by Nadav ] Cc: Kees Cook Cc: Peter Zijlstra Cc: Dave Hansen Reviewed-by: Masami Hiramatsu Tested-by: Masami Hiramatsu Signed-off-by: Andy Lutomirski Signed-off-by: Nadav Amit --- arch/x86/include/asm/mmu_context.h | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/arch/x86/include/asm/mmu_context.h b/arch/x86/include/asm/mmu_context.h index 0ca50611e8ce..7cc8e5c50bf6 100644 --- a/arch/x86/include/asm/mmu_context.h +++ b/arch/x86/include/asm/mmu_context.h @@ -338,4 +338,24 @@ static inline unsigned long __get_current_cr3_fast(void) return cr3; } +typedef struct { + struct mm_struct *prev; +} temporary_mm_state_t; + +static inline temporary_mm_state_t use_temporary_mm(struct mm_struct *mm) +{ + temporary_mm_state_t state; + + lockdep_assert_irqs_disabled(); + state.prev = this_cpu_read(cpu_tlbstate.loaded_mm); + switch_mm_irqs_off(NULL, mm, current); + return state; +} + +static inline void unuse_temporary_mm(temporary_mm_state_t prev) +{ + lockdep_assert_irqs_disabled(); + switch_mm_irqs_off(NULL, prev.prev, current); +} + #endif /* _ASM_X86_MMU_CONTEXT_H */ -- 2.17.1