search for: xc_dom_

Displaying 4 results from an estimated 4 matches for "xc_dom_".

Did you mean: xc_dom
2013 Nov 20
3
Invalid VA => ptr conversion with xc_dom_* API after XSA-55 fox
...f and FastIce pointed out a regression between Xen 4.1.2 and 4.1.6 when starting NetBSD domU; the kernel syms table gets slightly corrupted [1]. After dwelling into libxc code, FastIce noticed that changing back the return value to "ptr + offset" (instead of just "ptr") for xc_dom_vaddr_to_ptr() makes it work again. According to [2] while fixing XSA-55, Ian changed the "ptr + offset" return value to just "ptr". Is there a reason for this? IMHO the VA => ptr conversion should also take into account non-page aligned addresses, hence the offset (except...
2014 Nov 28
1
Bug#767295: xl: apparent memory leak
...commit 8f4023dd7d77de7b2c1af77e86637202a33f948a Author: Ian Campbell <ian.campbell at citrix.com> Date: Thu Nov 20 15:48:47 2014 +0000 libxc: don't leak buffer containing the uncompressed PV kernel The libxc xc_dom_* infrastructure uses a very simple malloc memory pool which is freed by xc_dom_release. However the various xc_try_*_decode routines (other than the gzip one) just use plain malloc/realloc and therefore the buffer ends up leaked. The memo...
2014 Nov 21
4
Bug#767295: [PATCH for-4.5 v2] libxc: don't leak buffer containing the uncompressed PV kernel
On 11/20/2014 03:21 PM, Konrad Rzeszutek Wilk wrote: > On Thu, Nov 20, 2014 at 03:48:47PM +0000, Ian Campbell wrote: >> The libxc xc_dom_* infrastructure uses a very simple malloc memory pool which >> is freed by xc_dom_release. However the various xc_try_*_decode routines (other >> than the gzip one) just use plain malloc/realloc and therefore the buffer ends >> up leaked. >> >> The memory pool currentl...
2014 Nov 21
1
Bug#767295: [PATCH for-4.5 v2] libxc: don't leak buffer containing the uncompressed PV kernel
On Thu, 2014-11-20 at 22:13 -0500, Gedalya wrote: > On 11/20/2014 03:21 PM, Konrad Rzeszutek Wilk wrote: > > On Thu, Nov 20, 2014 at 03:48:47PM +0000, Ian Campbell wrote: > >> The libxc xc_dom_* infrastructure uses a very simple malloc memory pool which > >> is freed by xc_dom_release. However the various xc_try_*_decode routines (other > >> than the gzip one) just use plain malloc/realloc and therefore the buffer ends > >> up leaked. > >> > >>...