From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 204175] nVMX: incorrect segment base calculation in VMX
Date: Sat, 10 Jan 2026 19:20:12 +0000 [thread overview]
Message-ID: <bug-204175-28872-o4HxAT2oD8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204175-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204175
Maxime Villard (max@m00nbsd.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |CODE_FIX
Summary|Segmentation: incorrect |nVMX: incorrect segment
|base calculation in VMX |base calculation in VMX
--- Comment #1 from Maxime Villard (max@m00nbsd.net) ---
This commit fixed the bug: 6694e48012826351036fd10fc506ca880023e25f.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-01-10 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 15:42 [Bug 204175] New: Segmentation: incorrect base calculation in VMX bugzilla-daemon
2026-01-10 19:20 ` 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-204175-28872-o4HxAT2oD8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox