From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sashiko Bot <sashiko-bot@kernel.org>,
Yan Zhao <yan.y.zhao@intel.com>,
Binbin Wu <binbin.wu@linux.intel.com>,
Ackerley Tng <ackerleytng@google.com>,
Haotian Jiang <jianghaotian.sunday@gmail.com>
Subject: Re: [PATCH v2 0/2] KVM: TDX: INIT_MEM_REGION fixes
Date: Mon, 21 Sep 2026 07:05:54 -0700 [thread overview]
Message-ID: <178999690496.715919.3769178910150533654.b4-ty@google.com> (raw)
In-Reply-To: <20260806170602.4112602-1-seanjc@google.com>
On Thu, 06 Aug 2026 10:06:00 -0700, Sean Christopherson wrote:
> I completely lost track of this, meant to post these patches weeks ago.
> Compile tested only.
>
> v2:
> - Fix an off-by-one bug.
> - Use gpa_t instead of raw u64.
> - Tweak the order of checks to bundle similar checks together, and to perform
> the super basic checks (alignment, size, etc.) first.
>
> [...]
Applied to kvm-x86 vmx, thanks!
[1/2] KVM: TDX: Reject INIT_MEM_REGION if number of bytes would overflow a u64
https://github.com/kvm-x86/linux/commit/7c9a2e3a4564
[2/2] KVM: TDX: Fix a benign off-by-one bug on the end GPA for INIT_MEM_REGION
https://github.com/kvm-x86/linux/commit/872aae89167c
--
https://github.com/kvm-x86/linux/tree/next
next prev parent reply other threads:[~2026-09-21 14:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 17:06 Sean Christopherson
2026-08-06 17:06 ` [PATCH v2 1/2] KVM: TDX: Reject INIT_MEM_REGION if number of bytes would overflow a u64 Sean Christopherson
2026-08-10 6:27 ` Yan Zhao
2026-08-10 8:45 ` Binbin Wu
2026-08-06 17:06 ` [PATCH v2 2/2] KVM: TDX: Fix a benign off-by-one bug on the end GPA for INIT_MEM_REGION Sean Christopherson
2026-08-10 6:58 ` Yan Zhao
2026-08-10 9:23 ` Binbin Wu
2026-09-21 14:05 ` Sean Christopherson [this message]
2026-09-22 18:05 ` [PATCH v2 0/2] KVM: TDX: INIT_MEM_REGION fixes Ackerley Tng
2026-09-22 18:50 ` Sean Christopherson
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=178999690496.715919.3769178910150533654.b4-ty@google.com \
--to=seanjc@google.com \
--cc=ackerleytng@google.com \
--cc=binbin.wu@linux.intel.com \
--cc=jianghaotian.sunday@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sashiko-bot@kernel.org \
--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®