All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 220963] nSVM: missing unmap in nested_svm_vmrun()
Date: Tue, 13 Jan 2026 17:32:16 +0000	[thread overview]
Message-ID: <bug-220963-28872-nAbsWhwVOZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220963-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220963

--- Comment #1 from yosry.ahmed@linux.dev ---
On Sat, Jan 10, 2026 at 07:33:25PM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=220963
> 
>             Bug ID: 220963
>            Summary: nSVM: missing unmap in nested_svm_vmrun()
>            Product: Virtualization
>            Version: unspecified
>           Hardware: AMD
>                 OS: Linux
>             Status: NEW
>           Severity: normal
>           Priority: P3
>          Component: kvm
>           Assignee: virtualization_kvm@kernel-bugs.osdl.org
>           Reporter: max@m00nbsd.net
>         Regression: No
> 
> In nested_svm_vmrun():
> 
>     ret = kvm_vcpu_map(vcpu, gpa_to_gfn(vmcb12_gpa), &map);
> ...
>     if (WARN_ON_ONCE(!svm->nested.initialized))
>         return -EINVAL;
> 
> A call to kvm_vcpu_unmap() is missing before the return.

I think I accidentally fixed this in
https://lore.kernel.org/kvm/20251215192722.3654335-26-yosry.ahmed@linux.dev/.

It's probably not a big deal, as reaching nested_svm_vmrun() without
svm->nested.initialized means we already have another bug :)

> 
> -- 
> You may reply to this email to add a comment.
> 
> You are receiving this mail because:
> You are watching the assignee of the bug.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2026-01-13 17:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-10 19:33 [Bug 220963] New: nSVM: missing unmap in nested_svm_vmrun() bugzilla-daemon
2026-01-13 17:32 ` Yosry Ahmed
2026-01-13 17:32 ` bugzilla-daemon [this message]

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=bug-220963-28872-nAbsWhwVOZ@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=kvm@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 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.