linux-kernel - Re: [PATCH] KVM: x86: use CPUID to locate host page table reserved bits

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: <20191211163641.91567206A5@mail.kernel.org>
Date:   Wed, 11 Dec 2019 16:36:40 +0000
From:   Sasha Levin <sashal@...nel.org>
To:     linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Cc:     stable@...r.kernel.org
Subject: Re: [PATCH] KVM: x86: use CPUID to locate host page table reserved bits

Hi,

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.4.2, v5.3.15, v4.19.88, v4.14.158, v4.9.206, v4.4.206.

v5.4.2: Build OK!
v5.3.15: Failed to apply! Possible dependencies:
    Unable to calculate

v4.19.88: Failed to apply! Possible dependencies:
    7b6f8a06e482 ("kvm: x86: Move kvm_set_mmio_spte_mask() from x86.c to mmu.c")
    f3ecb59dd49f ("kvm: x86: Fix reserved bits related calculation errors caused by MKTME")

v4.14.158: Failed to apply! Possible dependencies:
    7b6f8a06e482 ("kvm: x86: Move kvm_set_mmio_spte_mask() from x86.c to mmu.c")
    f3ecb59dd49f ("kvm: x86: Fix reserved bits related calculation errors caused by MKTME")

v4.9.206: Failed to apply! Possible dependencies:
    114df303a7ee ("kvm: x86: reduce collisions in mmu_page_hash")
    28a1f3ac1d0c ("kvm: x86: Set highest physical address bits in non-present/reserved SPTEs")
    312b616b30d8 ("kvm: x86: mmu: Set SPTE_SPECIAL_MASK within mmu.c")
    37f0e8fe6b10 ("kvm: x86: mmu: Do not use bit 63 for tracking special SPTEs")
    66d73e12f278 ("KVM: X86: MMU: no mmu_notifier_seq++ in kvm_age_hva")
    83ef6c8155c0 ("kvm: x86: mmu: Refactor accessed/dirty checks in mmu_spte_update/clear")
    97dceba29a6a ("kvm: x86: mmu: Fast Page Fault path retries")
    daa07cbc9ae3 ("KVM: x86: fix L1TF's MMIO GFN calculation")
    dcdca5fed5f6 ("x86: kvm: mmu: make spte mmio mask more explicit")
    ea4114bcd3a8 ("kvm: x86: mmu: Rename spte_is_locklessly_modifiable()")
    f160c7b7bb32 ("kvm: x86: mmu: Lockless access tracking for Intel CPUs without EPT A bits.")
    f3ecb59dd49f ("kvm: x86: Fix reserved bits related calculation errors caused by MKTME")

v4.4.206: Failed to apply! Possible dependencies:
    018aabb56d61 ("KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct")
    0e3d0648bd90 ("KVM: x86: MMU: always set accessed bit in shadow PTEs")
    114df303a7ee ("kvm: x86: reduce collisions in mmu_page_hash")
    14f4760562e4 ("kvm: set page dirty only if page has been writable")
    28a1f3ac1d0c ("kvm: x86: Set highest physical address bits in non-present/reserved SPTEs")
    37f0e8fe6b10 ("kvm: x86: mmu: Do not use bit 63 for tracking special SPTEs")
    83ef6c8155c0 ("kvm: x86: mmu: Refactor accessed/dirty checks in mmu_spte_update/clear")
    8d5cf1610da5 ("kvm: mmu: extend the is_present check to 32 bits")
    daa07cbc9ae3 ("KVM: x86: fix L1TF's MMIO GFN calculation")
    ea4114bcd3a8 ("kvm: x86: mmu: Rename spte_is_locklessly_modifiable()")
    f160c7b7bb32 ("kvm: x86: mmu: Lockless access tracking for Intel CPUs without EPT A bits.")
    f3ecb59dd49f ("kvm: x86: Fix reserved bits related calculation errors caused by MKTME")
    ffb128c89b77 ("kvm: mmu: don't set the present bit unconditionally")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks,
Sasha