mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	seanjc@google.com, yan.y.zhao@intel.com
Subject: Re: [PATCH] KVM: x86/mmu: Reject direct bits in gpa passed to KVM_PRE_FAULT_MEMORY
Date: Thu, 12 Jun 2025 13:41:30 +0800	[thread overview]
Message-ID: <d5f528c2-3518-4251-a50b-2d1f36c1662e@intel.com> (raw)
In-Reply-To: <CABgObfafukOFkeR09krA5GVb3itfpHNHjBM0aRZj5t4EKJv7Dw@mail.gmail.com>

On 6/12/2025 1:34 PM, Paolo Bonzini wrote:
> On Thu, Jun 12, 2025 at 7:29 AM Xiaoyao Li <xiaoyao.li@intel.com> wrote:
>>
>> On 6/12/2025 12:49 PM, Paolo Bonzini wrote:
>>> Only let userspace pass the same addresses that were used in KVM_SET_USER_MEMORY_REGION
>>> (or KVM_SET_USER_MEMORY_REGION2); gpas in the the upper half of the address space
>>> are an implementation detail of TDX and KVM.
>>>
>>> Extracted from a patch by Sean Christopherson <seanjc@google.com>.
>>>
>>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>>> ---
>>>    arch/x86/kvm/mmu/mmu.c | 3 +++
>>>    1 file changed, 3 insertions(+)
>>>
>>> diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c
>>> index a4040578b537..4e06e2e89a8f 100644
>>> --- a/arch/x86/kvm/mmu/mmu.c
>>> +++ b/arch/x86/kvm/mmu/mmu.c
>>> @@ -4903,6 +4903,9 @@ long kvm_arch_vcpu_pre_fault_memory(struct kvm_vcpu *vcpu,
>>>        if (!vcpu->kvm->arch.pre_fault_allowed)
>>>                return -EOPNOTSUPP;
>>>
>>> +     if (kvm_is_gfn_alias(vcpu->kvm, gpa_to_gfn(range->gpa)))
>>> +             return -EINVAL;
>>
>> Do we need to worry about the case (range->gpa + range->size) becomes alias?
> 
> No, because the function only processes a single page and everything
> in the non-aliased part of the address space *can* be prefaulted.
> 
> KVM's generic kvm_vcpu_pre_fault_memory() call will see the EINVAL on
> a later invocation and will stop processing the part of the request
> that is has the shared/direct bit set.

reasonable..

Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>

> Paolo
> 
>>
>>>        /*
>>>         * reload is efficient when called repeatedly, so we can do it on
>>>         * every iteration.
>>
> 
> 


  reply	other threads:[~2025-06-12  5:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12  4:49 Paolo Bonzini
2025-06-12  5:29 ` Xiaoyao Li
2025-06-12  5:34   ` Paolo Bonzini
2025-06-12  5:41     ` Xiaoyao Li [this message]
2025-06-13  3:00 ` Yan Zhao
2025-06-13 20:16   ` Sean Christopherson
2025-06-16  2:04     ` Yan Zhao

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=d5f528c2-3518-4251-a50b-2d1f36c1662e@intel.com \
    --to=xiaoyao.li@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=yan.y.zhao@intel.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 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®