linux-kernel - Re: [PATCH 0/2] KVM: x86: Fix dangling page reference in TDP MMU

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <452f3642-04fd-aa32-920e-5ad5925c0c91@redhat.com>
Date:   Mon, 13 Dec 2021 16:06:49 +0100
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Ignat Korchagin <ignat@...udflare.com>,
        linux-kernel <linux-kernel@...r.kernel.org>, kvm@...r.kernel.org
Cc:     Sean Christopherson <seanjc@...gle.com>, bgardon@...gle.com,
        dmatlack@...gle.com, stevensd@...omium.org,
        kernel-team <kernel-team@...udflare.com>
Subject: Re: [PATCH 0/2] KVM: x86: Fix dangling page reference in TDP MMU

On 12/13/21 14:43, Ignat Korchagin wrote:
> The only difference I noticed is the presence of __tdp_mmu_set_spte
> between zap_gfn_range and __handle_changed_spte, which is absent from
> the original stacktrace.

That's just a difference in inlining decisions, so it doesn't really matter.

Let's see if Sean has some more ideas or finds something obviously wrong 
in my patch.

Paolo