Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Paolo Bonzini" <pbonzini@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 34/45] KVM: x86/mmu: Adjust gva_to_gpa to allow returning an error
Date: Mon, 02 Nov 2026 18:19:33 +0000	[thread overview]
Message-ID: <sashiko-outbox-193925@kernel.org> (raw)
In-Reply-To: <20261102174512.8903-18-pbonzini@redhat.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] KVM: x86: mismatch between KVM_TRANSLATE docs and -EFAULT handling
- [Medium] KVM: x86: unconditional gva_to_gpa() walk in kvm_fixup_and_inject_pf_error()
--

commit 914d25167c243b05b87b4e07ce157df3731ce832
Author: Paolo Bonzini <pbonzini@redhat.com>

KVM: x86/mmu: Adjust gva_to_gpa to allow returning an error

This commit changes the gva_to_gpa callback and its helper wrappers to return
an int error code while writing the translated guest physical address to an
out parameter, allowing callers to distinguish -EFAULT from INVALID_GPA.

> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> index ac8cd51bdadae..743a738ff8d39 100644
> --- a/Documentation/virt/kvm/api.rst
> +++ b/Documentation/virt/kvm/api.rst
> @@ -521,7 +521,9 @@ data structures.
>  :Architectures: x86
>  :Type: vcpu ioctl
>  :Parameters: struct kvm_translation (in/out)
> -:Returns: 0 on success, -1 on error
> +:Returns: 0 on success, -1 on error.  errno is EFAULT if
> +          the parameter is invalid but also if guest memory
> +          could not be accessed
>  
>  Translates a virtual address according to the vcpu's current address
>  translation mode.

[ ... ]

> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index bb36ca1106e58..53400fda9f44b 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c

[ ... ]

> @@ -9341,19 +9354,24 @@ int kvm_arch_vcpu_ioctl_translate(struct kvm_vcpu *vcpu,
>  {
>  	unsigned long vaddr = tr->linear_address;
>  	gpa_t gpa;
> -	int idx;
> +	int idx, r;
>  
>  	vcpu_load(vcpu);
> -
>  	idx = srcu_read_lock(&vcpu->kvm->srcu);
> -	gpa = kvm_mmu_gva_to_gpa_system(vcpu, vaddr, NULL);
> +	r = kvm_mmu_gva_to_gpa_system(vcpu, vaddr, &gpa, NULL);
>  	srcu_read_unlock(&vcpu->kvm->srcu, idx);
> +	vcpu_put(vcpu);
> +
> +	if (r) {
> +		if (r != -EFAULT)
> +			return r;
> +		gpa = INVALID_GPA;
> +	}
> +
>  	tr->physical_address = gpa;
>  	tr->valid = gpa != INVALID_GPA;
>  	tr->writeable = 1;
>  	tr->usermode = 0;
> -
> -	vcpu_put(vcpu);
>  	return 0;
>  }

[Severity: Medium]
Documentation/virt/kvm/api.rst is updated above to state that KVM_TRANSLATE
returns -1 with errno set to EFAULT when guest memory could not be accessed.

However, in kvm_arch_vcpu_ioctl_translate(), when kvm_mmu_gva_to_gpa_system()
returns -EFAULT, the error is caught and converted into gpa = INVALID_GPA,
causing the ioctl to return 0 with tr->valid = 0 instead of returning -EFAULT.

Should kvm_arch_vcpu_ioctl_translate() propagate -EFAULT to userspace, or was
the intention to report an invalid translation (tr->valid = 0) and the
documentation in api.rst needs to be updated to match?

> @@ -10815,11 +10833,15 @@ int kvm_fixup_and_inject_pf_error(struct kvm_vcpu *vcpu, gva_t gva, u16 error_co
>  {
>  	struct kvm_pagewalk *gva_walk = &vcpu->arch.gva_walk;
>  	struct x86_exception fault;
> +	gpa_t gpa;
> +	int r;
>  	u64 access = error_code &
>  		(PFERR_WRITE_MASK | PFERR_FETCH_MASK | PFERR_USER_MASK);
>  
> -	if (!(error_code & PFERR_PRESENT_MASK) ||
> -	    gva_walk->gva_to_gpa(vcpu, gva_walk, gva, access, &fault) != INVALID_GPA) {
> +	r = gva_walk->gva_to_gpa(vcpu, gva_walk, gva, access, &gpa, &fault);
> +	if (r)
> +		return r;
> +	if (!(error_code & PFERR_PRESENT_MASK) || gpa != INVALID_GPA) {
>  		/*
>  		 * If gva_walk->gva_to_gpa succeeded, the page
>  		 * tables probably do not match the TLB.  Just proceed

[Severity: Medium]
Previously, kvm_fixup_and_inject_pf_error() short-circuited and skipped
calling gva_walk->gva_to_gpa() whenever !(error_code & PFERR_PRESENT_MASK) was
true.

With gva_walk->gva_to_gpa() hoisted before the PFERR_PRESENT_MASK check, every
non-present page fault reaching kvm_fixup_and_inject_pf_error() (for instance,
in nested VMX when vmx_need_pf_intercept() causes prepare_vmcs02_rare() to
intercept all L2 page faults) now walks the guest and nested page tables even
though both gpa and fault are overwritten in the if-block when
PFERR_PRESENT_MASK is clear.

Aside from the extra page-table walk, if a guest PTE was concurrently made
present or upper-level guest PTEs are walked, FNAME(walk_addr_generic)() can
update guest Accessed/Dirty bits or return -EFAULT on a non-present fault.

Should gva_walk->gva_to_gpa() only be called when (error_code &
PFERR_PRESENT_MASK) is set?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261102174130.8779-1-pbonzini@redhat.com?part=34

  reply	other threads:[~2026-11-02 18:19 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 17:40 [PATCH v4 00/45] KVM: x86: Introduce memory protection attributes Paolo Bonzini
2026-11-02 17:40 ` [PATCH 01/45] KVM: nVMX/nSVM: check unconditionally whether CR3 is valid Paolo Bonzini
2026-11-02 18:05   ` sashiko-bot
2026-11-02 17:40 ` [PATCH 02/45] KVM: x86/hyperv: do not overwrite hc->ingpa for SIGNAL_EVENT hypercall Paolo Bonzini
2026-11-02 17:40 ` [PATCH 03/45] KVM: x86: apply nGPA->GPA translation to KVM_HC_CLOCK_PAIRING Paolo Bonzini
2026-11-02 17:40 ` [PATCH 04/45] KVM: x86/emulate: Check TSS busy-bit writes during task switches Paolo Bonzini
2026-11-02 18:22   ` sashiko-bot
2026-11-02 17:40 ` [PATCH 05/45] KVM: loongarch: do full validity check on the gfn-to-hva cache Paolo Bonzini
2026-11-02 17:40 ` [PATCH 06/45] KVM: selftests: Test address translation for Hyper-V direct L2 hypercalls Paolo Bonzini
2026-11-02 17:40 ` [PATCH 07/45] KVM: selftests: Take into account mixed memory fault flags Paolo Bonzini
2026-11-02 17:50   ` sashiko-bot
2026-11-02 17:40 ` [PATCH 08/45] selftests: kvm: drop TEST_ASSERT_SUPPORTED_ATTRIBUTES Paolo Bonzini
2026-11-02 17:40 ` [PATCH 09/45] KVM: Define and communicate KVM_EXIT_MEMORY_FAULT RWX flags to userspace Paolo Bonzini
2026-11-02 17:55   ` sashiko-bot
2026-11-02 17:40 ` [PATCH 10/45] KVM: x86: Introduce memory fault on invalid hypercalls reads/writes Paolo Bonzini
2026-11-02 17:40 ` [PATCH 11/45] KVM: selftests: test hypercall memory fault exits Paolo Bonzini
2026-11-02 17:58   ` sashiko-bot
2026-11-02 17:40 ` [PATCH 12/45] KVM: x86/mmu: intersect writability from __kvm_faultin_pfn with fault->map_writable Paolo Bonzini
2026-11-02 17:40 ` [PATCH 13/45] KVM: x86/mmu: Extend map_writable to a full ACC_* mask Paolo Bonzini
2026-11-02 17:40 ` [PATCH 14/45] KVM: x86/mmu: Init memslot hugepage information for non-private_mem VMs too Paolo Bonzini
2026-11-02 17:40 ` [PATCH 15/45] KVM: VMX: return error from kvm_set_cr* Paolo Bonzini
2026-11-02 17:41 ` [PATCH 16/45] KVM: adjust for presence of more than one attribute Paolo Bonzini
2026-11-02 18:03   ` sashiko-bot
2026-11-02 17:44 ` [PATCH 17/45] KVM: Introduce NR/NW/NX memory attributes Paolo Bonzini
2026-11-02 18:04   ` sashiko-bot
2026-11-03  9:25   ` kernel test robot
2026-11-02 17:44 ` [PATCH 18/45] KVM: Include memory protections in result of gfn->hva conversion Paolo Bonzini
2026-11-02 17:44 ` [PATCH 19/45] KVM: Introduce kvm_fetch_guest_page() and use it for x86 Paolo Bonzini
2026-11-02 17:44 ` [PATCH 20/45] KVM: Take memory protections into account for memory read/write/fetch Paolo Bonzini
2026-11-02 17:44 ` [PATCH 21/45] KVM: Take memory protections into account for __kvm_vcpu_map Paolo Bonzini
2026-11-02 17:44 ` [PATCH 22/45] KVM: Encapsulate memattrs array into anonymous struct Paolo Bonzini
2026-11-02 17:44 ` [PATCH 23/45] KVM: Introduce kvm_check_gen()/kvm_memslots_check_gen() Paolo Bonzini
2026-11-02 18:04   ` sashiko-bot
2026-11-03 18:07   ` kernel test robot
2026-11-02 17:44 ` [PATCH 24/45] KVM: Introduce a generation number for memory attributes Paolo Bonzini
2026-11-02 18:20   ` sashiko-bot
2026-11-03 14:11   ` kernel test robot
2026-11-02 17:44 ` [PATCH 25/45] KVM: Take memory protections into account for accesses with cached gfn->hva Paolo Bonzini
2026-11-02 18:14   ` sashiko-bot
2026-11-02 17:44 ` [PATCH 26/45] KVM: pfncache: Fail to refresh if it contains memory protections Paolo Bonzini
2026-11-02 18:09   ` sashiko-bot
2026-11-02 17:44 ` [PATCH 27/45] KVM: x86/mmu: Do not prefetch sptes on gfns backed by memory attributes Paolo Bonzini
2026-11-02 17:44 ` [PATCH 28/45] KVM: x86/mmu: Take memory protection attributes into account during faults Paolo Bonzini
2026-11-02 18:26   ` sashiko-bot
2026-11-02 17:44 ` [PATCH 29/45] KVM: x86/emulate: change return value of emulator_io_permitted to int Paolo Bonzini
2026-11-02 17:44 ` [PATCH 30/45] KVM: x86/emulate: Propagate memory faults to userspace Paolo Bonzini
2026-11-02 18:32   ` sashiko-bot
2026-11-02 17:44 ` [PATCH 31/45] KVM: x86: "Handle" failed decode when skipping instructions Paolo Bonzini
2026-11-02 18:18   ` sashiko-bot
2026-11-02 17:44 ` [PATCH 32/45] KVM: vmx/sgx: make return value of sgx_gva_to_gpa consistent with its callers Paolo Bonzini
2026-11-02 17:45 ` [PATCH 33/45] KVM: x86: Allow page fault fixup to return errors Paolo Bonzini
2026-11-02 17:45 ` [PATCH 34/45] KVM: x86/mmu: Adjust gva_to_gpa to allow returning an error Paolo Bonzini
2026-11-02 18:19   ` sashiko-bot [this message]
2026-11-02 17:45 ` [PATCH 35/45] KVM: x86/mmu: Propagate errors from nested GPA translation Paolo Bonzini
2026-11-02 17:45 ` [PATCH 36/45] KVM: x86: Propagate memory faults through load_pdptrs() Paolo Bonzini
2026-11-02 18:29   ` sashiko-bot
2026-11-02 17:45 ` [PATCH 37/45] KVM: x86/mmu: Issue memory fault exit if walk failed due to memory attribute Paolo Bonzini
2026-11-02 18:32   ` sashiko-bot
2026-11-02 17:45 ` [PATCH 38/45] KVM: x86: mark VM as dead after KVM_SET_SREGS fails to load PDPTRs Paolo Bonzini
2026-11-02 18:28   ` sashiko-bot
2026-11-02 17:45 ` [PATCH 39/45] KVM: VMX: mark VM dead on shadow VMCS or eVMCS access failures Paolo Bonzini
2026-11-02 18:40   ` sashiko-bot
2026-11-02 17:45 ` [PATCH 40/45] KVM: let kvm_arch_post_set_memory_attributes drop mmu_lock Paolo Bonzini
2026-11-02 17:45 ` [PATCH 41/45] KVM: x86/mmu: Obsolete all roots if memattr contains gPTEs Paolo Bonzini
2026-11-02 17:45 ` [PATCH 42/45] KVM: x86: selftests: Introduce memory protection attributes test Paolo Bonzini
2026-11-02 18:43   ` sashiko-bot
2026-11-02 17:45 ` [PATCH 43/45] KVM: x86: selftests: Introduce memory attributes PTE test Paolo Bonzini
2026-11-02 17:45 ` [PATCH 44/45] KVM: x86: selftests: Introduce memory attributes side-channel tests Paolo Bonzini
2026-11-02 18:41   ` sashiko-bot
2026-11-02 17:45 ` [PATCH 45/45] KVM: x86: split out parts of load_pdptrs Paolo Bonzini
2026-11-03 14:40 ` [syzbot ci] Re: KVM: x86: Introduce memory protection attributes syzbot ci

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=sashiko-outbox-193925@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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