linux-kernel - [tip:x86/urgent] x86/kvm/vmx: Remove duplicate l1d flush definitions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <tip-94d7a86c21a3d6046bf4616272313cb7d525075a@git.kernel.org>
Date:   Mon, 20 Aug 2018 09:12:27 -0700
From:   tip-bot for Josh Poimboeuf <tipbot@...or.com>
To:     linux-tip-commits@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org, mingo@...nel.org,
        pbonzini@...hat.com, jpoimboe@...hat.com, hpa@...or.com,
        tglx@...utronix.de
Subject: [tip:x86/urgent] x86/kvm/vmx: Remove duplicate l1d flush
 definitions

Commit-ID:  94d7a86c21a3d6046bf4616272313cb7d525075a
Gitweb:     https://git.kernel.org/tip/94d7a86c21a3d6046bf4616272313cb7d525075a
Author:     Josh Poimboeuf <jpoimboe@...hat.com>
AuthorDate: Tue, 14 Aug 2018 12:32:19 -0500
Committer:  Thomas Gleixner <tglx@...utronix.de>
CommitDate: Mon, 20 Aug 2018 18:04:43 +0200

x86/kvm/vmx: Remove duplicate l1d flush definitions

These are already defined higher up in the file.

Fixes: 7db92e165ac8 ("x86/kvm: Move l1tf setup function")
Signed-off-by: Josh Poimboeuf <jpoimboe@...hat.com>
Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
Cc: Paolo Bonzini <pbonzini@...hat.com>
Cc: stable@...r.kernel.org
Link: https://lkml.kernel.org/r/d7ca03ae210d07173452aeed85ffe344301219a5.1534253536.git.jpoimboe@redhat.com

---
 arch/x86/kvm/vmx.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 46b428c0990e..4be481c72f60 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -9726,9 +9726,6 @@ static int vmx_handle_exit(struct kvm_vcpu *vcpu)
  * information but as all relevant affected CPUs have 32KiB L1D cache size
  * there is no point in doing so.
  */
-#define L1D_CACHE_ORDER 4
-static void *vmx_l1d_flush_pages;
-
 static void vmx_l1d_flush(struct kvm_vcpu *vcpu)
 {
 	int size = PAGE_SIZE << L1D_CACHE_ORDER;