Re: Re: WARNING in x86_emulate_insn

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

Re: Re: WARNING in x86_emulate_insn

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

Re: WARNING in x86_emulate_insn

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

Re: WARNING in x86_emulate_insn

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

Re: Re: WARNING in x86_emulate_insn

On 12/8/2017 5:27 PM, Wanpeng Li wrote: 2017-12-08 16:28 GMT+08:00 Tianyu Lan : Hi Jim: Thanks for your help. 2017-12-08 5:25 GMT+08:00 Jim Mattson : Try disabling the module parameter, "unrestricted_guest." Make sure that the module

Re: Re: WARNING in x86_emulate_insn

On 12/8/2017 5:27 PM, Wanpeng Li wrote: 2017-12-08 16:28 GMT+08:00 Tianyu Lan : Hi Jim: Thanks for your help. 2017-12-08 5:25 GMT+08:00 Jim Mattson : Try disabling the module parameter, "unrestricted_guest." Make sure that the module parameter, "emulate_invalid_guest_state" is

Re: WARNING in x86_emulate_insn

2017-12-08 16:28 GMT+08:00 Tianyu Lan : > Hi Jim: > Thanks for your help. > > 2017-12-08 5:25 GMT+08:00 Jim Mattson : >> Try disabling the module parameter, "unrestricted_guest." Make sure >> that the module parameter,

Re: WARNING in x86_emulate_insn

2017-12-08 16:28 GMT+08:00 Tianyu Lan : > Hi Jim: > Thanks for your help. > > 2017-12-08 5:25 GMT+08:00 Jim Mattson : >> Try disabling the module parameter, "unrestricted_guest." Make sure >> that the module parameter, "emulate_invalid_guest_state" is enabled. >> This combination allows

Re: WARNING in x86_emulate_insn

2017-12-08 16:44 GMT+08:00 Ingo Molnar : > > * Tianyu Lan wrote: > >> Hi Jim: >> Thanks for your help. >> >> 2017-12-08 5:25 GMT+08:00 Jim Mattson : >> > Try disabling the module parameter, "unrestricted_guest." Make sure >>

Re: WARNING in x86_emulate_insn

2017-12-08 16:44 GMT+08:00 Ingo Molnar : > > * Tianyu Lan wrote: > >> Hi Jim: >> Thanks for your help. >> >> 2017-12-08 5:25 GMT+08:00 Jim Mattson : >> > Try disabling the module parameter, "unrestricted_guest." Make sure >> > that the module parameter, "emulate_invalid_guest_state" is

Re: WARNING in x86_emulate_insn

* Tianyu Lan wrote: > Hi Jim: > Thanks for your help. > > 2017-12-08 5:25 GMT+08:00 Jim Mattson : > > Try disabling the module parameter, "unrestricted_guest." Make sure > > that the module parameter, "emulate_invalid_guest_state" is

Re: WARNING in x86_emulate_insn

* Tianyu Lan wrote: > Hi Jim: > Thanks for your help. > > 2017-12-08 5:25 GMT+08:00 Jim Mattson : > > Try disabling the module parameter, "unrestricted_guest." Make sure > > that the module parameter, "emulate_invalid_guest_state" is enabled. > > This combination allows userspace to

Re: WARNING in x86_emulate_insn

Hi Jim: Thanks for your help. 2017-12-08 5:25 GMT+08:00 Jim Mattson : > Try disabling the module parameter, "unrestricted_guest." Make sure > that the module parameter, "emulate_invalid_guest_state" is enabled. > This combination allows userspace to feed invalid

Re: WARNING in x86_emulate_insn

Hi Jim: Thanks for your help. 2017-12-08 5:25 GMT+08:00 Jim Mattson : > Try disabling the module parameter, "unrestricted_guest." Make sure > that the module parameter, "emulate_invalid_guest_state" is enabled. > This combination allows userspace to feed invalid guest state into the >

Re: WARNING in x86_emulate_insn

2017-12-08 11:22 GMT+08:00 syzbot : > syzkaller has found reproducer for the following crash on > 968edbd93c0cbb40ab48aca972392d377713a0c3 > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master > compiler:

Re: WARNING in x86_emulate_insn

2017-12-08 11:22 GMT+08:00 syzbot : > syzkaller has found reproducer for the following crash on > 968edbd93c0cbb40ab48aca972392d377713a0c3 > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console output is

Re: WARNING in x86_emulate_insn

Try disabling the module parameter, "unrestricted_guest." Make sure that the module parameter, "emulate_invalid_guest_state" is enabled. This combination allows userspace to feed invalid guest state into the in-kernel emulator. On Thu, Dec 7, 2017 at 2:40 AM, Wanpeng Li

Re: WARNING in x86_emulate_insn

Try disabling the module parameter, "unrestricted_guest." Make sure that the module parameter, "emulate_invalid_guest_state" is enabled. This combination allows userspace to feed invalid guest state into the in-kernel emulator. On Thu, Dec 7, 2017 at 2:40 AM, Wanpeng Li wrote: > 2017-12-07 15:52

Re: WARNING in x86_emulate_insn

2017-12-07 15:52 GMT+08:00 Wanpeng Li : > 2017-12-07 15:49 GMT+08:00 蓝天宇 : >> Hi Dmitry: >> I tried to reproduce the issue via syz-execprog with attached >> reproducer on latest linux-next but it causes VM-entry failure due to >> invalid guest

Re: WARNING in x86_emulate_insn

2017-12-07 15:52 GMT+08:00 Wanpeng Li : > 2017-12-07 15:49 GMT+08:00 蓝天宇 : >> Hi Dmitry: >> I tried to reproduce the issue via syz-execprog with attached >> reproducer on latest linux-next but it causes VM-entry failure due to >> invalid guest state... > > Because rflags is 0 in his program.

Re: WARNING in x86_emulate_insn

2017-12-07 15:49 GMT+08:00 蓝天宇 : > Hi Dmitry: > I tried to reproduce the issue via syz-execprog with attached > reproducer on latest linux-next but it causes VM-entry failure due to > invalid guest state... Because rflags is 0 in his program. You can set ept=0 and

Re: WARNING in x86_emulate_insn

2017-12-07 15:49 GMT+08:00 蓝天宇 : > Hi Dmitry: > I tried to reproduce the issue via syz-execprog with attached > reproducer on latest linux-next but it causes VM-entry failure due to > invalid guest state... Because rflags is 0 in his program. You can set ept=0 and retry. Regards, Wanpeng Li

Re: WARNING in x86_emulate_insn

Hi Dmitry: I tried to reproduce the issue via syz-execprog with attached reproducer on latest linux-next but it causes VM-entry failure due to invalid guest state... 2017-12-07 14:25 GMT+08:00 Dmitry Vyukov : > On Thu, Dec 7, 2017 at 1:44 AM, Wanpeng Li

Re: WARNING in x86_emulate_insn

Hi Dmitry: I tried to reproduce the issue via syz-execprog with attached reproducer on latest linux-next but it causes VM-entry failure due to invalid guest state... 2017-12-07 14:25 GMT+08:00 Dmitry Vyukov : > On Thu, Dec 7, 2017 at 1:44 AM, Wanpeng Li wrote: >> 2017-12-06 4:07 GMT+08:00

Re: WARNING in x86_emulate_insn

On Thu, Dec 7, 2017 at 1:44 AM, Wanpeng Li wrote: > 2017-12-06 4:07 GMT+08:00 syzbot > : >> Hello, >> >> syzkaller hit the following crash on >> fb20eb9d798d2f4c1a75b7fe981d72dfa8d7270d >>

Re: WARNING in x86_emulate_insn

On Thu, Dec 7, 2017 at 1:44 AM, Wanpeng Li wrote: > 2017-12-06 4:07 GMT+08:00 syzbot > : >> Hello, >> >> syzkaller hit the following crash on >> fb20eb9d798d2f4c1a75b7fe981d72dfa8d7270d >> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master >> compiler: gcc (GCC) 7.1.1

Re: WARNING in x86_emulate_insn

2017-12-06 4:07 GMT+08:00 syzbot : > Hello, > > syzkaller hit the following crash on > fb20eb9d798d2f4c1a75b7fe981d72dfa8d7270d > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC)

Re: WARNING in x86_emulate_insn

2017-12-06 4:07 GMT+08:00 syzbot : > Hello, > > syzkaller hit the following crash on > fb20eb9d798d2f4c1a75b7fe981d72dfa8d7270d > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console output is attached. >