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

[Xen-devel] mmap() on pvops will not return FAILED if the memory can't be mapped or accessed.


  • To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Wang, Shane" <shane.wang@xxxxxxxxx>
  • Date: Thu, 7 Jan 2010 16:27:36 +0800
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc: "Hao, Xudong" <xudong.hao@xxxxxxxxx>
  • Delivery-date: Thu, 07 Jan 2010 00:29:23 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcqPc0QZqn+wLtrVQ9yJC7blkhj0Uw==
  • Thread-topic: mmap() on pvops will not return FAILED if the memory can't be mapped or accessed.

Jeremy,

I wrote an application calling mmap() on pvops and found it will not return 
FAILED if the mapped memory (say TXT heap) can't be mapped or accessed, unlike 
2.6.18 domain 0 and the latest kernel.

The serial port outputs (XEN) mm.c:776:d0 Non-privileged (0) attempt to map I/O 
space 000af520...000af5ff, which is the same as the output of 2.6.18 dom0.
However, then it outputs many lines like (XEN) mm.c:838:d0 Error getting mfn 
ac247 (pfn a38aa) from L1 entry 80000000ac247425 for l1e_owner=0, 
pg_owner=32753....
This behaviour may cause dom0 hang finally.

Is it correct? Can you help to have a look at it?

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


 


Rackspace

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