Thanks for your reply :)
I'm confused that it throw an exception "NULL pointer dereference" when
implement "mov 0x45114(%rip),%rax" instruction. Because "0x45114(%rip)" couldn't be NULL.
Will thread stack overflow result in Oops which is hard to explain like this?
Reproducing is ongoing...
Regards~
On 2016/8/15 20:50, Radim Krčmář wrote:
> 2016-08-12 17:08+0800, Xiexiangyou:
>> Kvm vm runs in hardware server with intel broadwell CPU. A oops exception occurs.
>>
>> kernel version: 3.0.93
>> kvm version: 3.6
>> CPU: And the CPU is Intel(R) Xeon(R) CPU E5-2618L v4 @ 2.20GHz.
>>
>> The message as follows :
>> <1>[25808.222049] BUG: unable to handle kernel NULL pointer dereference at (null)
>> <1>[25808.230539] IP: [<ffffffffa021f3c5>] vcpu_enter_guest+0x555/0x790 [kvm]
>> <4>[25808.237496] PGD 0
>> <1>[25808.239839] Thread overran stack, or stack corrupted
>
> This could be an imporant lead. Stack overrun usually happened with xfs
> or similar operations, but your kernel does not look standard ...
> Can you reproduce after increasing the stack size with 6538b8ea886e
> ("x86_64: expand kernel stack to 16K")?
>
> .
>
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
