search for: xenmem_exchang

...upstream Justification: user security hole Hi, the following vulnerability was published for xen. CVE-2017-7228[0]: | An issue (known as XSA-212) was discovered in Xen, with fixes available | for 4.8.x, 4.7.x, 4.6.x, 4.5.x, and 4.4.x. The earlier XSA-29 fix | introduced an insufficient check on XENMEM_exchange input, allowing the | caller to drive hypervisor memory accesses outside of the guest | provided input/output arrays. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https...

...510 / XSA-26: Grant table version switch list corruption vulnerability * CVE-2012-5511 / XSA-27: several HVM operations do not validate the range of their inputs * CVE-2012-5512 / XSA-28: HVMOP_get_mem_access crash / HVMOP_set_mem_access information leak * CVE-2012-5513 / XSA-29: XENMEM_exchange may overwrite hypervisor memory * CVE-2012-5514 / XSA-30: Broken error handling in guest_physmap_mark_populate_on_demand() * CVE-2012-5515 / XSA-31: Several memory hypercall operations allow invalid extent order values We recommend all users of the 4.1 stable series to update to this la...

...black trees. The p2m tracks physical to machine and machine to physical mappings. Given that we assume a 1:1 mapping in dom0, the only entries in both trees are grant refs that have been mapped in dom0. Another consequence of the new approach is that the hypercalls we were previously introducing (XENMEM_exchange_and_pin, XENMEM_pin, XENMEM_unpin) are not needed anymore. This latest version doesn''t need any hypervisor changes anymore. Cheers, Stefano Changes in v8: - use __phys_to_pfn and __pfn_to_phys in phys_to_dma and dma_to_phys; - cast 0 to dma_addr_t in the definition of DMA_ERROR_CODE;...

This patch series contains a set of patches making minios rather easier to use, from an application development point of view. Overview of patches: 1 Command line argument parsing support, from Xen. 2 Weak console handler function. 3 Build system tweaks for application directories. 4 Trailing whitespace cleanup. (because it is very messy) Patch 4 is likely to be more controversial than