Quoting Dwight Engen (dwight.en...@oracle.com):
> On Wed, 25 Sep 2013 14:44:07 -0400
> S.Çağlar Onur <cag...@10ur.org> wrote:
> 
> > Uhh something is wrong with this commit
> 
> Hey Serge, I think this has to do with the rebase after the split up as
> it certinaly wasn't seg faulting on me originally. The split also

Yeah, sorry.  I'd lost the free(line) when moving code.  I'm not quite
sure how the lxc_cgroup_process_info_free(info) at the out3: label could
have actually worked for you, but maybe I dropped a zeroing out of
something somewhere.

> appears to have introduced a couple new leaks (ie. line in the
> subfunctions). Do you want me to just redo the cleanup fds & memory
> stuff on top of your change?

If you see any more bits I stupidly dropped in current git head,
please do.  I'm going to get going on the selinux patch now.

thanks,
-serge

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Lxc-devel mailing list
Lxc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-devel

Reply via email to