Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	stable@vger.kernel.org,  Hyunwoo Kim <imv4bel@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] KVM: x86: Check for invalid/obsolete root *after* making MMU pages available
Date: Tue, 11 Aug 2026 10:49:59 +0900	[thread overview]
Message-ID: <anp_WfTodatOEOZ1@google.com> (raw)
In-Reply-To: <anpVAhjqvBvIuoa0@google.com>

On (26/08/10 15:47), Sean Christopherson wrote:
[..]
> is_page_fault_stale() needs be checked for the TDP MMU as well.  I had the
> pleasure of doing this cherry-pick for an internal kernel, this is what I thought
> yielded the easiest-to-read sequence:

I knew it!

>         if (is_tdp_mmu_fault) {
>                 read_lock(&vcpu->kvm->mmu_lock);
>         } else {
>                 write_lock(&vcpu->kvm->mmu_lock);
> 
>                 r = make_mmu_pages_available(vcpu);
>                 if (r)
>                         goto out_unlock;
>         }
> 
>         if (is_page_fault_stale(vcpu, fault, mmu_seq)) {
>                 r = RET_PF_RETRY;
>                 goto out_unlock;
>         }
> 
>         if (is_tdp_mmu_fault)
>                 r = kvm_tdp_mmu_map(vcpu, fault);
>         else
>                 r = __direct_map(vcpu, fault);
> 
> As a diff...

Sean, can I trouble you with a request to submit your cherry-pick to 6.1.y?

  reply	other threads:[~2026-08-11  1:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-08  6:22 [PATCH] KVM: x86: Check for invalid/obsolete root *after* making MMU pages available Sergey Senozhatsky
2026-08-08  6:27 ` Sergey Senozhatsky
2026-08-10 14:08   ` Sean Christopherson
2026-08-10 14:40     ` Sergey Senozhatsky
2026-08-10 22:47 ` Sean Christopherson
2026-08-11  1:49   ` Sergey Senozhatsky [this message]
2026-08-10 23:57 ` Sasha Levin
  -- strict thread matches above, loose matches on Subject: below --
2026-07-21 10:28 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=anp_WfTodatOEOZ1@google.com \
    --to=senozhatsky@chromium.org \
    --cc=imv4bel@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=stable@vger.kernel.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