All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Woodhouse <dwmw@amazon.co.uk>,
	Mingwei Zhang <mizhang@google.com>,
	Sean Christopherson <seanjc@google.com>
Subject: [PATCH 0/2] KVM: Fix mmu_notifier vs. pfncache race
Date: Wed, 20 Apr 2022 00:48:57 +0000	[thread overview]
Message-ID: <20220420004859.3298837-1-seanjc@google.com> (raw)

Fix a race between mmu_notifier invalidation and pfncache refresh, and
then fix another race of sorts within pfncache that exists because of the
hacky approach pfncache currently employs to try and handle races with
mmu_notifiers.

Both issues were found by inspection and not proven on hardware.

Sean Christopherson (2):
  KVM: Fix race between mmu_notifier invalidation and pfncache refresh
  KVM: Do not speculatively mark pfn cache valid to "fix" race

 virt/kvm/kvm_main.c |  9 ++++++
 virt/kvm/pfncache.c | 79 +++++++++++++++++++++++++++++----------------
 2 files changed, 61 insertions(+), 27 deletions(-)


base-commit: 150866cd0ec871c765181d145aa0912628289c8a
-- 
2.36.0.rc0.470.gd361397f0d-goog


             reply	other threads:[~2022-04-20  0:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  0:48 Sean Christopherson [this message]
2022-04-20  0:48 ` [PATCH 1/2] KVM: Fix race between mmu_notifier invalidation and pfncache refresh Sean Christopherson
2022-04-20  0:48 ` [PATCH 2/2] KVM: Do not speculatively mark pfn cache valid to "fix" race Sean Christopherson
2022-04-20 10:41 ` [PATCH 0/2] KVM: Fix mmu_notifier vs. pfncache race Paolo Bonzini

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=20220420004859.3298837-1-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=dwmw@amazon.co.uk \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mizhang@google.com \
    --cc=pbonzini@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.