From: Avi Kivity <avi@redhat.com>
To: Huang Ying <ying.huang@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
"masbock@linux.vnet.ibm.com" <masbock@linux.vnet.ibm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/2] KVM, Fix QEMU-KVM is killed by guest SRAO MCE
Date: Wed, 28 Apr 2010 12:47:53 +0300 [thread overview]
Message-ID: <4BD80449.4010700@redhat.com> (raw)
In-Reply-To: <1272423375.24125.189.camel@yhuang-dev.sh.intel.com>
On 04/28/2010 05:56 AM, Huang Ying wrote:
>
>>>
>>> Just want to use the side effect of copy_from_user, SIGBUS will be sent
>>> to current process because the page touched is marked as poisoned. That
>>> is, failure is expected, so the return value is not checked.
>>>
>>>
>> What if the failure doesn't happen? Say, someone mmap()ed over the page.
>>
> Sorry, not get your idea clearly. hva is re-mmap()ed? We just read the
> hva, not write, so I think it should be OK here.
>
>
We don't generate a signal in this case. Does the code continue to work
correctly (not sure what correctly is in this case... should probably
just continue).
There's also the possibility of -EFAULT.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-04-28 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 7:04 [PATCH 2/2] KVM, Fix QEMU-KVM is killed by guest SRAO MCE Huang Ying
2010-04-27 7:47 ` Avi Kivity
2010-04-27 9:25 ` Huang Ying
2010-04-27 9:30 ` Avi Kivity
2010-04-28 2:56 ` Huang Ying
2010-04-28 9:47 ` Avi Kivity [this message]
2010-04-29 1:31 ` Huang Ying
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=4BD80449.4010700@redhat.com \
--to=avi@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masbock@linux.vnet.ibm.com \
--cc=ying.huang@intel.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