On Thu, Jan 10, 2013 at 10:05:39AM +0800, Liu Bo wrote: > On Tue, Jan 08, 2013 at 12:07:34PM -0800, Zach Brown wrote: > > > This is for detecting extent map leak. > > > > Hmm, I guess it's cool to get the allocation-specific decoding which you > > don't get from the generic kernel leak tracking? > > Thanks for the advice, but what allocation-specific decoding do you refer to? > Could you please show me any examples?
IMHO that there's a leak check that is targeted to one exact problem in one subsystem (extent_map in btrfs), does not need to be poked to do a scan-for-leaks so the leak can be reported immediatelly and not after some time. It makes sense for such a core structure like extent_map. Other structures are allocated from a slab so we can at least check for leaks upon module unload. david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
