All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lan Tianyu <tianyu.lan@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Tianyu Lan <lantianyu1986@gmail.com>,
	Jim Mattson <jmattson@google.com>
Cc: Wanpeng Li <kernellwp@gmail.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	syzbot
	<bot+75375385991b4f8c599704a10849863c586ea284@syzkaller.appspotmail.com>,
	"H. Peter Anvin" <hpa@zytor.com>, kvm <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>, Radim Krcmar <rkrcmar@redhat.com>,
	syzkaller-bugs@googlegroups.com,
	Thomas Gleixner <tglx@linutronix.de>,
	the arch/x86 maintainers <x86@kernel.org>
Subject: Re: Re: WARNING in x86_emulate_insn
Date: Tue, 12 Dec 2017 16:50:11 +0800	[thread overview]
Message-ID: <cbbf4f41-db88-d238-4eef-47b4f9582229@intel.com> (raw)
In-Reply-To: <ec6ee88f-1d56-9bb9-53a9-41e4c9e800d8@redhat.com>

On 2017年12月12日 06:45, Paolo Bonzini wrote:
> On 08/12/2017 09:28, Tianyu Lan wrote:
>> I find this is pop instruction emulation issue. According "SDM VOL2,
>> chapter INSTRUCTION
>> SET REFERENCE. POP—Pop a Value from the Stack"
>>
>> Protected Mode Exceptions
>> #GP(0) If attempt is made to load SS register with NULL segment selector.
> 
> This is not what the testcase is testing; this is already covered by 
> __load_segment_descriptor:
> 
>         if (null_selector) {
>                 if (seg == VCPU_SREG_CS || seg == VCPU_SREG_TR)
>                         goto exception;
> 
>                 if (seg == VCPU_SREG_SS) {
>                         if (ctxt->mode != X86EMUL_MODE_PROT64 || rpl != cpl)
>                                 goto exception;
> 		...
> 	}

Yes, __load_segment_descriptor() does such check. I find em_pop doesn't
load SS segment. SS isn't loaded before calling em_pop in the test case.
Should this be fixed?

> 
> Is there a path that can return X86EMUL_PROPAGATE_FAULT without setting
> ctxt->exception.vector and/or without going through emulate_exception?
> 
> I don't think it's possible to write a test in kvm-unit-tests, because the
> state has "impossible" segment descriptor cache contents.

Sent out a fix patch for the issue. Please have a look. Thanks.
https://marc.info/?l=kvm&m=151306208214733&w=2

> 
> Paolo
> 
>> This test case hits it but current code doesn't check such case.
>> The following patch can fix the issue.
>>
>> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
>> index abe74f7..e2ac5cc 100644
>> --- a/arch/x86/kvm/emulate.c
>> +++ b/arch/x86/kvm/emulate.c
>> @@ -1844,6 +1844,9 @@ static int emulate_pop(struct x86_emulate_ctxt *ctxt,
>>         int rc;
>>         struct segmented_address addr;
>>
>> +       if ( !get_segment_selector(ctxt, VCPU_SREG_SS))
>> +               return emulate_gp(ctxt, 0);
>> +
>>         addr.ea = reg_read(ctxt, VCPU_REGS_RSP) & stack_mask(ctxt);
>>         addr.seg = VCPU_SREG_SS;
>>         rc = segmented_read(ctxt, addr, dest, len);
> 


-- 
Best regards
Tianyu Lan

  reply	other threads:[~2017-12-12  9:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 20:07 WARNING in x86_emulate_insn syzbot
2017-12-07  0:44 ` Wanpeng Li
2017-12-07  6:25   ` Dmitry Vyukov
2017-12-07  7:49     ` 蓝天宇
2017-12-07  7:52       ` Wanpeng Li
2017-12-07 10:40         ` Wanpeng Li
2017-12-07 21:25           ` Jim Mattson
2017-12-08  8:28             ` Tianyu Lan
2017-12-08  8:44               ` Ingo Molnar
2017-12-08  8:48                 ` Tianyu Lan
2017-12-08  9:27               ` Wanpeng Li
2017-12-09  5:44                 ` Lan, Tianyu
2017-12-11 22:45               ` Paolo Bonzini
2017-12-12  8:50                 ` Lan Tianyu [this message]
2017-12-08  3:22 ` syzbot
2017-12-08  3:33   ` Wanpeng Li

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=cbbf4f41-db88-d238-4eef-47b4f9582229@intel.com \
    --to=tianyu.lan@intel.com \
    --cc=bot+75375385991b4f8c599704a10849863c586ea284@syzkaller.appspotmail.com \
    --cc=dvyukov@google.com \
    --cc=hpa@zytor.com \
    --cc=jmattson@google.com \
    --cc=kernellwp@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=lantianyu1986@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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.