Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2713631imu; Sat, 10 Nov 2018 22:37:19 -0800 (PST) X-Google-Smtp-Source: AJdET5f3w0wBs+IfSgqGbh2ekfPta5tGvh7FO+x4kw/K6TJ+e8nnz54xHkPRwwIULROFAfawY2jq X-Received: by 2002:a17:902:6a87:: with SMTP id n7-v6mr12286353plk.86.1541918239643; Sat, 10 Nov 2018 22:37:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541918239; cv=none; d=google.com; s=arc-20160816; b=y73/HauB6asYSg3myTM+jD8EnNqkd4cSntS1Gi6QqPtsGwp4iH9WSVRRkF0e7uvxF7 I60AzANhT6q9HkRaq/xAEnDM/P+wgyA6lfNkv27B0Hd2o/aGAXGPPK2wnpFrpfxDKq5/ B41VLMCANc8vY9z8TVHsrV+nzGo8t1KMEyyXfzAtczPsNq0NCYTOQpmeFY733Fa19ldr QBlPolts/E/JaUgT5D+IyJbQHuz6/cg1ulc9zHii6w0QUV4i2ePvzEpEQNIiRoDdVbUn 4eKeFBZotAoUpQEkVYEY5rLg9mAgQXX2QrIyNG9FKRlg9xeXN5ykQPvNGc83u30HtyI2 kQ+Q== 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=AqIfq1zMSQviM27dhK7pnt3PVSm787RZzwMNPaYPQtfOmIPsEzlO043OAXh5SO0tSE XzAWfLaDhABuoA6izfkrqgB68BrLoEgvNrui9Q9SEKl+whhfyvRmislxKdRJ8c1LmUHA PWISwCkSY8MR4e/43OUAj4JFYmZu0Pw8foSYrSQBtjXFzDFHA3v+1rN5ehB3/M+8UntQ EpTGhy3v64JyuEdCXOg6M02qgcZ4JdAGvvSay4xBJya5wxOZKgI7gOcWrra0GZRMnrQO 7zAhJq468FjulTFkNmn8qq1tVi3N++kNFiN0a0DtZUVwPlDJ/FhawEneNXeyYGrl8FHE F2TA== 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 bj7-v6si13556132plb.193.2018.11.10.22.36.31; Sat, 10 Nov 2018 22:37:19 -0800 (PST) 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 S1727803AbeKKQXH (ORCPT + 99 others); Sun, 11 Nov 2018 11:23:07 -0500 Received: from ex13-edg-ou-002.vmware.com ([208.91.0.190]:35773 "EHLO EX13-EDG-OU-002.vmware.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727307AbeKKQXG (ORCPT ); Sun, 11 Nov 2018 11:23:06 -0500 Received: from sc9-mailhost3.vmware.com (10.113.161.73) by EX13-EDG-OU-002.vmware.com (10.113.208.156) with Microsoft SMTP Server id 15.0.1156.6; Sat, 10 Nov 2018 22:35:05 -0800 Received: from sc2-haas01-esx0118.eng.vmware.com (sc2-haas01-esx0118.eng.vmware.com [10.172.44.118]) by sc9-mailhost3.vmware.com (Postfix) with ESMTP id 5246E4077D; Sat, 10 Nov 2018 22:35:24 -0800 (PST) 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 v4 03/10] x86/mm: temporary mm struct Date: Sat, 10 Nov 2018 15:17:25 -0800 Message-ID: <20181110231732.15060-4-namit@vmware.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20181110231732.15060-1-namit@vmware.com> References: <20181110231732.15060-1-namit@vmware.com> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: None (EX13-EDG-OU-002.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