[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH v2 0/5] xenstore: fix memory leak of xenstored
xenstored has a memory leak when setting watches: a no longer active watch which fired in the past will still use some memory. This is critical for long running connections to xenstored like the qemu process serving as a qdisk backend for dom0. It will use some few kB in xenstored for each domain create/destroy pair. Fix this leak by using a temporary memory context for all allocations in xenstored when firing a watch event. Changes in V2: - modified patch description as requested by Ian Jackson - split up patch 2 as requested by Ian Jackson Juergen Gross (5): xenstore: call each xenstored command function with temporary context xenstore: add explicit memory context parameter to get_parent() xenstore: add explicit memory context parameter to read_node() xenstore: add explicit memory context parameter to get_node() xenstore: use temporary memory context for firing watches tools/xenstore/xenstored_core.c | 108 ++++++++++++++++++--------------- tools/xenstore/xenstored_core.h | 4 ++ tools/xenstore/xenstored_domain.c | 20 +++--- tools/xenstore/xenstored_domain.h | 10 +-- tools/xenstore/xenstored_transaction.c | 5 +- tools/xenstore/xenstored_transaction.h | 2 +- tools/xenstore/xenstored_watch.c | 14 +++-- tools/xenstore/xenstored_watch.h | 3 +- 8 files changed, 94 insertions(+), 72 deletions(-) -- 2.6.6 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |