From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Xiexiangyou <xiexiangyou@huawei.com>
Cc: kvm@vger.kernel.org, guangrong.xiao@linux.intel.com, pbonzini@redhat.com
Subject: Re: [RFH] NULL pointer dereference oops occurs when running kvm VM
Date: Tue, 16 Aug 2016 18:49:32 +0200 [thread overview]
Message-ID: <20160816164931.GA22826@potion> (raw)
In-Reply-To: <787289f9-ef25-5b25-6b01-e557db57cb44@huawei.com>
2016-08-16 16:25+0800, Xiexiangyou:
> 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?
Probably not, but it is easy to rule out. Can't trust anything in a
corrupted system ...
prev parent reply other threads:[~2016-08-16 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 9:08 [RFH] NULL pointer dereference oops occurs when running kvm VM Xiexiangyou
[not found] ` <57AD9821.6010804@windriver.com>
2016-08-14 8:45 ` Xiexiangyou
[not found] ` <20160815125011.GA16471@potion>
2016-08-16 8:25 ` Xiexiangyou
2016-08-16 16:49 ` Radim Krčmář [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=20160816164931.GA22826@potion \
--to=rkrcmar@redhat.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=xiexiangyou@huawei.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