On Mon, 26 Nov 2012 11:40:40 -0600 Serge Hallyn <serge.hal...@canonical.com> wrote:
> Quoting Dwight Engen (dwight.en...@oracle.com): > > Valgrind showed use of ->next field after item has been free()ed. > > Introduce a lxc_list_for_each_safe() which allows traversal of a > > list when the body of the loop may remove the currently iterated > > item. > > > > Signed-off-by: Dwight Engen <dwight.en...@oracle.com> > > Thanks (boy do I feel like an idiot) > > Acked-by: Serge E. Hallyn <serge.hal...@ubuntu.com> No big deal, I guess it would only affect the threaded case where another thread picked up the free()ed memory as we iterated. I only noticed because of valgrind :) ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
