From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Eugene Korenevsky <ekorenevsky@gmail.com>,
kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v5 2/3] kvm: vmx: segment limit check: use access length
Date: Fri, 7 Jun 2019 08:01:39 -0700 [thread overview]
Message-ID: <20190607150139.GC9083@linux.intel.com> (raw)
In-Reply-To: <20190607060321.GA29109@dnote>
On Fri, Jun 07, 2019 at 09:03:21AM +0300, Eugene Korenevsky wrote:
> There is an imperfection in get_vmx_mem_address(): access length is
> ignored when checking the limit. To fix this, pass access length as a
> function argument. The value of access length is obvious since it is
> used by callers after get_vmx_mem_address() call.
>
> Signed-off-by: Eugene Korenevsky <ekorenevsky@gmail.com>
Reviewed-by: Sean Christopherson <sean.j.christopherson@intel.com>
prev parent reply other threads:[~2019-06-07 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 6:03 [PATCH v5 2/3] kvm: vmx: segment limit check: use access length Eugene Korenevsky
2019-06-07 15:01 ` Sean Christopherson [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=20190607150139.GC9083@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=ekorenevsky@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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 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.