> - local = mem_get0(this->local_pool); > + local = GF_CALLOC (sizeof (*local), 1, gf_crypt_mt_local); As I understand it, mem_get0 is a valid (and even more efficient) way to allocate such objects. The frame cleanup code should recognize which method to use when deallocating. If that's broken, we're going to have more numerous and serious problems than this. I'll look into it further. _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
