From: Paolo Bonzini <pbonzini@redhat.com>
To: Ignat Korchagin <ignat@cloudflare.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org
Cc: Sean Christopherson <seanjc@google.com>,
bgardon@google.com, dmatlack@google.com, stevensd@chromium.org,
kernel-team <kernel-team@cloudflare.com>
Subject: Re: [PATCH 0/2] KVM: x86: Fix dangling page reference in TDP MMU
Date: Mon, 13 Dec 2021 16:06:49 +0100 [thread overview]
Message-ID: <452f3642-04fd-aa32-920e-5ad5925c0c91@redhat.com> (raw)
In-Reply-To: <CALrw=nEM6LEAD8LA1Bd15=8BK=TFwwwAMKy_DWRrDkD=r+1Tqg@mail.gmail.com>
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
next prev parent reply other threads:[~2021-12-13 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 11:25 Paolo Bonzini
2021-12-13 11:25 ` [PATCH 1/2] KVM: x86: allow kvm_tdp_mmu_zap_invalidated_roots with write-locked mmu_lock Paolo Bonzini
2021-12-13 11:25 ` [PATCH 2/2] KVM: x86: zap invalid roots in kvm_tdp_mmu_zap_all Paolo Bonzini
2021-12-13 16:36 ` Sean Christopherson
2021-12-14 19:45 ` Sean Christopherson
2021-12-13 13:43 ` [PATCH 0/2] KVM: x86: Fix dangling page reference in TDP MMU Ignat Korchagin
2021-12-13 15:06 ` Paolo Bonzini [this message]
2021-12-13 16:47 ` Sean Christopherson
2021-12-13 18:28 ` Paolo Bonzini
2021-12-13 19:44 ` Sean Christopherson
2021-12-13 20:18 ` Ignat Korchagin
2021-12-14 3:12 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=452f3642-04fd-aa32-920e-5ad5925c0c91@redhat.com \
--to=pbonzini@redhat.com \
--cc=bgardon@google.com \
--cc=dmatlack@google.com \
--cc=ignat@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--cc=stevensd@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®