Received: by 2002:a05:7412:251c:b0:e2:908c:2ebd with SMTP id w28csp1729998rda; Tue, 24 Oct 2023 01:08:25 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFfhTzsQ9OMDMbpSnFhw5H2l2sCNPOqMICIAR3DCx7xqmFWvgjaz7wq6GTQkfNAHdNZCGaH X-Received: by 2002:a62:f24d:0:b0:68f:cd71:45d5 with SMTP id y13-20020a62f24d000000b0068fcd7145d5mr9845379pfl.3.1698134905092; Tue, 24 Oct 2023 01:08:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1698134905; cv=none; d=google.com; s=arc-20160816; b=iuLjAZqeD8iReSzrsaQryxKTtmiNHLnVUnh9RAdfTZLI05bi8Z8Oh6SJUhtLAByX2n Hao1PWSSFXRIsHftlIHb/pP1Xfjn/P5p4khsKgL8hlVtJ6+ZgGSd7MS9SAK4UB/xzF6l A4q91ESVOebcxmwVxUrqIDATt0LrF74UvyKlbaU0/dNb8gI+HNDNwUoeb0qI5pebIHU8 f59fWIO9GZupm5okIEwo0MG9QMqoqzJXaJHsP59BW72sK6EXLOyNDwV96HNIZMJZ2Bzm huLARuLuVSfhPTvZL0xaA1shWtcHv1TBriup1h3OTXcrmuUegJRMwu9vMqEcX9IhA2FH ux3A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-disposition:mime-version:message-id :subject:cc:to:from:date:dkim-signature; bh=io1HSxMi2XA0Lo0fCtX/gRJBxYvpcBYOoN5rveWT6yA=; fh=9IMLg7jvt1SH4vuOuAikoxXI6bAHTeHqfdDJLIho67U=; b=UaZEvMbgE79OKsVePhKpkkUsEraV7gM062pn5Km64t0EpETBCuVvdh/2e+JdIu9Qyu CJt4qIjtDAIl2OdWLH2FcmwWwW5FhiGOWCE5aCoSu/1OlSUA5goPCdz++MHLeKzH8ICJ ZSQ8/dDGuXGXVfS2B6dCnoWduz1LaG35Iboe1sr15G48TzmOJhUmpVmQpJq5PZz/sr0T XK6zOv/7xvnrmZK5rKiudF2qC/7sLrvZ7h8nqKcmLgsMg5h3FNMmIvQnLtNc4BkmkGP6 efpPFMhbzg0dDRLmk9Xh7IFit5UZKv/Woy4cFtEvaDrvuM34r2lNay4D7ZqBKx+pYGDM JfaQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=R7fdfk71; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from snail.vger.email (snail.vger.email. [23.128.96.37]) by mx.google.com with ESMTPS id e6-20020aa79806000000b006be044f21efsi7983505pfl.362.2023.10.24.01.08.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 Oct 2023 01:08:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) client-ip=23.128.96.37; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=R7fdfk71; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by snail.vger.email (Postfix) with ESMTP id 05AEA8031B25; Tue, 24 Oct 2023 01:08:24 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at snail.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233746AbjJXIIV (ORCPT + 99 others); Tue, 24 Oct 2023 04:08:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38488 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232893AbjJXIIU (ORCPT ); Tue, 24 Oct 2023 04:08:20 -0400 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.9]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BDA9E111; Tue, 24 Oct 2023 01:08:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1698134898; x=1729670898; h=date:from:to:cc:subject:message-id:mime-version; bh=u9rCyLGSdVulRiJpx/JNudLmp34NwQVv3IZ33EiSu+4=; b=R7fdfk71NMH6n6WlHwA65OCKjSzTszV4JqZIf0AwrmvzpkKbsord7JfA Hj+bv1lKyAbl8e8I9HAsoSlx+THJUL791iZcNK+pa92z6kyFGkFR2eT5S fbJj/KNaBeqKsHBL3c7E73dZFhSqbLjxqIYd77NgT56BhFJLauJZyG3/D C8Pm+aiEoT+CEPCwGeMYNmX73tUhD0+YNZvmGAQpnnqJfWpRvJqUk0OzE TimbIMQL/RJWHkIr2YR9lnmUTqtXag+XPdO+XsDQXahiAHXhos2tloi/e v0AhR4379GF+vxM4nm4tLwI8/watBX+W91TYdU4E1jY3bn52wrA/ZM5zk g==; X-IronPort-AV: E=McAfee;i="6600,9927,10872"; a="5632674" X-IronPort-AV: E=Sophos;i="6.03,247,1694761200"; d="scan'208";a="5632674" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orvoesa101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Oct 2023 01:08:18 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10872"; a="824215388" X-IronPort-AV: E=Sophos;i="6.03,247,1694761200"; d="scan'208";a="824215388" Received: from zijianw1-mobl.amr.corp.intel.com (HELO desk) ([10.209.109.187]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Oct 2023 01:08:16 -0700 Date: Tue, 24 Oct 2023 01:08:14 -0700 From: Pawan Gupta To: Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , Peter Zijlstra , Josh Poimboeuf , Andy Lutomirski , Jonathan Corbet , Sean Christopherson , Paolo Bonzini , tony.luck@intel.com, ak@linux.intel.com, tim.c.chen@linux.intel.com Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, kvm@vger.kernel.org, Alyssa Milburn , Daniel Sneddon , antonio.gomez.iglesias@linux.intel.com, Pawan Gupta , Alyssa Milburn , Dave Hansen Subject: [PATCH v2 0/6] Delay VERW Message-ID: <20231024-delay-verw-v2-0-f1881340c807@linux.intel.com> X-B4-Tracking: v=1; b=H4sIAFZ2N2UC/03MSw6CMBSF4a2QO7akD6ziyH0YBthe5CZYTIsVQ rp3mzpxeP7kfDsE9IQBLtUOHiMFml0e8lCBGXv3QEY2b5BcKsGFYBanfmMR/YdZ3pya9qzv0ij Ih5fHgdaC3QC6XEYKy+y3okdR+g+S/B+KgnFmhuHY8FYrqe11Ivdea3ILTrWZn9CllL7H3khrr AAAAA== X-Mailer: b4 0.12.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=1.0 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00, DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF, RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (snail.vger.email [0.0.0.0]); Tue, 24 Oct 2023 01:08:24 -0700 (PDT) v2: - Removed the extra EXEC_VERW macro layers. (Sean) - Move NOPL before VERW. (Sean) - s/USER_CLEAR_CPU_BUFFERS/CLEAR_CPU_BUFFERS/. (Josh/Dave) - Removed the comments before CLEAR_CPU_BUFFERS. (Josh) - Remove CLEAR_CPU_BUFFERS from NMI returning to kernel and document the reason. (Josh/Dave) - Reformat comment in md_clear_update_mitigation(). (Josh) - Squash "x86/bugs: Cleanup mds_user_clear" patch. (Nikolay) - s/GUEST_CLEAR_CPU_BUFFERS/CLEAR_CPU_BUFFERS/. (Josh) - Added a patch from Sean to use CFLAGS.CF for VMLAUNCH/VMRESUME selection. This facilitates a single CLEAR_CPU_BUFFERS location for both VMLAUNCH and VMRESUME. (Sean) v1: https://lore.kernel.org/r/20231020-delay-verw-v1-0-cff54096326d@linux.intel.com Hi, Legacy instruction VERW was overloaded by some processors to clear micro-architectural CPU buffers as a mitigation of CPU bugs. This series moves VERW execution to a later point in exit-to-user path. This is needed because in some cases it may be possible for kernel data to be accessed after VERW in arch_exit_to_user_mode(). Such accesses may put data into MDS affected CPU buffers, for example: 1. Kernel data accessed by an NMI between VERW and return-to-user can remain in CPU buffers (since NMI returning to kernel does not execute VERW to clear CPU buffers). 2. Alyssa reported that after VERW is executed, CONFIG_GCC_PLUGIN_STACKLEAK=y scrubs the stack used by a system call. Memory accesses during stack scrubbing can move kernel stack contents into CPU buffers. 3. When caller saved registers are restored after a return from function executing VERW, the kernel stack accesses can remain in CPU buffers(since they occur after VERW). Although these cases are less practical to exploit, moving VERW closer to ring transition reduces the attack surface. Overview of the series: Patch 1: Prepares VERW macros for use in asm. Patch 2: Adds macros to 64-bit entry/exit points. Patch 3: Adds macros to 32-bit entry/exit points. Patch 4: Enables the new macros. Patch 5: Uses CFLAGS.CF for VMLAUNCH/VMRESUME selection. Patch 6: Adds macro to VMenter. Below is some performance data collected with v1 on a Skylake client compared with previous implementation: Baseline: v6.6-rc5 | Test | Configuration | Relative | | ------------------ | ---------------------- | -------- | | build-linux-kernel | defconfig | 1.00 | | hackbench | 32 - Process | 1.02 | | nginx | Short Connection - 500 | 1.01 | Signed-off-by: Pawan Gupta --- Pawan Gupta (5): x86/bugs: Add asm helpers for executing VERW x86/entry_64: Add VERW just before userspace transition x86/entry_32: Add VERW just before userspace transition x86/bugs: Use ALTERNATIVE() instead of mds_user_clear static key KVM: VMX: Move VERW closer to VMentry for MDS mitigation Sean Christopherson (1): KVM: VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH Documentation/arch/x86/mds.rst | 39 ++++++++++++++++++++++++++---------- arch/x86/entry/entry_32.S | 3 +++ arch/x86/entry/entry_64.S | 11 ++++++++++ arch/x86/entry/entry_64_compat.S | 1 + arch/x86/include/asm/cpufeatures.h | 2 +- arch/x86/include/asm/entry-common.h | 1 - arch/x86/include/asm/nospec-branch.h | 31 +++++++++++++++++----------- arch/x86/kernel/cpu/bugs.c | 15 ++++++-------- arch/x86/kernel/nmi.c | 2 -- arch/x86/kvm/vmx/run_flags.h | 7 +++++-- arch/x86/kvm/vmx/vmenter.S | 10 ++++++--- arch/x86/kvm/vmx/vmx.c | 10 ++++++--- 12 files changed, 88 insertions(+), 44 deletions(-) --- base-commit: 05d3ef8bba77c1b5f98d941d8b2d4aeab8118ef1 change-id: 20231011-delay-verw-d0474986b2c3 Best regards, -- Thanks, Pawan