[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [RFO] Action when bad address passed in hypercall by guest

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 19 Mar 2009 17:07:34 +0000
Cc:
Delivery-date: Thu, 19 Mar 2009 10:09:00 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: AcmotHbdOuHjubMtTXmzuCqE1S1fqQAALs8p
Thread-topic: [Xen-devel] [RFO] Action when bad address passed in hypercall by guest

On 19/03/2009 17:01, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> hat is the appropriate action if the gfn is "bad" (specifically
> fails the p2m_ram_rw test from gfn_to_mfn)?
> 
> A) Ignore it (but return an error from the hypercall)
> B) __domain_crash() as the guest is surely broken or malicious

Probably return an error to the caller.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

References:
- [Xen-devel] [RFO] Action when bad address passed in hypercall by guest
  - From: Dan Magenheimer

Prev by Date: Re: [Xen-devel] question about patch 13252
Next by Date: [Xen-devel] Re: Question about x86/mm/gup.c's use of disabled interrupts
Previous by thread: [Xen-devel] [RFO] Action when bad address passed in hypercall by guest
Next by thread: [Xen-devel] [PATCH] fs-backend: fix gnttab unmap
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.