From: Maxim Levitsky <mlevitsk@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+760a73552f47a8cd0fd9@syzkaller.appspotmail.com,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Hou Wenlong <houwenlong.hwl@antgroup.com>
Subject: Re: [PATCH 1/3] KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks
Date: Tue, 12 Jul 2022 16:35:08 +0300 [thread overview]
Message-ID: <8307c007823eac899d3a017d1616e0d08a653185.camel@redhat.com> (raw)
In-Reply-To: <20220711232750.1092012-2-seanjc@google.com>
On Mon, 2022-07-11 at 23:27 +0000, Sean Christopherson wrote:
> Wait to mark the TSS as busy during LTR emulation until after all fault
> checks for the LTR have passed. Specifically, don't mark the TSS busy if
> the new TSS base is non-canonical.
Took me a while to notice it but I see the canonical check now, so the patch
makes sense, and so:
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
Unrelated, but I do wonder why we use cmpxchg_emulated for setting the busy bit, while we use
write_segment_descriptor to set the accessed bit.
Best regards,
Maxim Levitsky
>
> Opportunistically drop the one-off !seg_desc.PRESENT check for TR as the
> only reason for the early check was to avoid marking a !PRESENT TSS as
> busy, i.e. the common !PRESENT is now done before setting the busy bit.
>
> Fixes: e37a75a13cda ("KVM: x86: Emulator ignores LDTR/TR extended base on LLDT/LTR")
> Reported-by: syzbot+760a73552f47a8cd0fd9@syzkaller.appspotmail.com
> Cc: stable@vger.kernel.org
> Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
> Cc: Hou Wenlong <houwenlong.hwl@antgroup.com>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> arch/x86/kvm/emulate.c | 19 +++++++++----------
> 1 file changed, 9 insertions(+), 10 deletions(-)
>
> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
> index 39ea9138224c..09e4b67b881f 100644
> --- a/arch/x86/kvm/emulate.c
> +++ b/arch/x86/kvm/emulate.c
> @@ -1699,16 +1699,6 @@ static int __load_segment_descriptor(struct x86_emulate_ctxt *ctxt,
> case VCPU_SREG_TR:
> if (seg_desc.s || (seg_desc.type != 1 && seg_desc.type != 9))
> goto exception;
> - if (!seg_desc.p) {
> - err_vec = NP_VECTOR;
> - goto exception;
> - }
> - old_desc = seg_desc;
> - seg_desc.type |= 2; /* busy */
> - ret = ctxt->ops->cmpxchg_emulated(ctxt, desc_addr, &old_desc, &seg_desc,
> - sizeof(seg_desc), &ctxt->exception);
> - if (ret != X86EMUL_CONTINUE)
> - return ret;
> break;
> case VCPU_SREG_LDTR:
> if (seg_desc.s || seg_desc.type != 2)
> @@ -1749,6 +1739,15 @@ static int __load_segment_descriptor(struct x86_emulate_ctxt *ctxt,
> ((u64)base3 << 32), ctxt))
> return emulate_gp(ctxt, 0);
> }
> +
> + if (seg == VCPU_SREG_TR) {
> + old_desc = seg_desc;
> + seg_desc.type |= 2; /* busy */
> + ret = ctxt->ops->cmpxchg_emulated(ctxt, desc_addr, &old_desc, &seg_desc,
> + sizeof(seg_desc), &ctxt->exception);
> + if (ret != X86EMUL_CONTINUE)
> + return ret;
> + }
> load:
> ctxt->ops->set_segment(ctxt, selector, &seg_desc, base3, seg);
> if (desc)
next prev parent reply other threads:[~2022-07-12 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 23:27 [PATCH 0/3] KVM: x86: Fix fault-related bugs in LTR/LLDT emulation Sean Christopherson
2022-07-11 23:27 ` [PATCH 1/3] KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks Sean Christopherson
2022-07-12 13:35 ` Maxim Levitsky [this message]
2022-07-12 17:29 ` Sean Christopherson
2022-07-11 23:27 ` [PATCH 2/3] KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP Sean Christopherson
2022-07-12 13:37 ` Maxim Levitsky
2022-07-12 17:31 ` Sean Christopherson
2022-07-11 23:27 ` [PATCH 3/3] KVM: x86: WARN only once if KVM leaves a dangling userspace I/O request Sean Christopherson
2022-07-12 13:34 ` Maxim Levitsky
2022-07-12 1:07 ` [PATCH 0/3] KVM: x86: Fix fault-related bugs in LTR/LLDT emulation Nadav Amit
2022-07-14 18:20 ` 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=8307c007823eac899d3a017d1616e0d08a653185.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=houwenlong.hwl@antgroup.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=seanjc@google.com \
--cc=syzbot+760a73552f47a8cd0fd9@syzkaller.appspotmail.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®