Re: port-xen/47057: Xen NetBSD DomU file system trash under Linux Dom0

[Roger Pau Monné <royger%NetBSD.org@localhost>]

The following reply was made to PR port-xen/47057; it has been noted by GNATS.

From: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= <royger%NetBSD.org@localhost>
To: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
Cc: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= <roger.pau%citrix.com@localhost>, 
        "gnats-bugs%NetBSD.org@localhost" <gnats-bugs%netbsd.org@localhost>, 
        "port-xen-maintainer%netbsd.org@localhost" 
<port-xen-maintainer%netbsd.org@localhost>, 
        "gnats-admin%netbsd.org@localhost" <gnats-admin%netbsd.org@localhost>, 
"netbsd-bugs%netbsd.org@localhost" <netbsd-bugs%netbsd.org@localhost>
Subject: Re: port-xen/47057: Xen NetBSD DomU file system trash under Linux Dom0
Date: Sun, 21 Oct 2012 20:10:36 +0200

 On Sun, Oct 21, 2012 at 8:00 PM, Manuel Bouyer 
<bouyer%antioche.eu.org@localhost> wrote:
 > Does linux do this silently, or does it complain when the ring
 > corruption occurs ?
 
 With the patch attached in the previous post, we will do the same as
 Linux (reset indexes and printk). I've never seen that happen in
 Linux, so I'm not sure if there's anything else.
 
 >> Is it possible that someone writes to the machine address
 >> xen_start_info.store_mfn and is there anyway to check that nobody is
 >> mapping this ma to another va?
 >
 > I've been thinking about checking this, but it's harder to do.
 > Maybe it's easier to do this check in the hypervisor ?
 
 Will check that, not sure if there's an easy way to this in the hypervisor.