+++ This bug was initially created as a clone of Bug #1235927 +++ Description of problem: In dht_migration_complete_check_task, ret = inode_ctx_reset1 (inode, this, &tmp_miginfo); if (tmp_miginfo) { GF_FREE (tmp_miginfo); goto out; } However, another fop might be still using miginfo while we free it. The correct way to solve this is to use refcounting mechanism of memory management. Version-Release number of selected component (if applicable): How reproducible: Found through code-review. Its a race that can happen while doing parallel operations on a file during migration. Since its a race, it might not be reproducible consistently Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Anand Avati on 2015-06-26 02:25:28 EDT --- REVIEW: http://review.gluster.org/11418 (cluster/dht: use refcount to manage memory used to store migration information.) posted (#1) for review on master by Raghavendra G (rgowdapp)
REVIEW: http://review.gluster.org/11419 (cluster/dht: use refcount to manage memory used to store migration information.) posted (#1) for review on release-3.7 by Raghavendra G (rgowdapp)
REVIEW: http://review.gluster.org/11419 (cluster/dht: use refcount to manage memory used to store migration information.) posted (#2) for review on release-3.7 by Raghavendra G (rgowdapp)
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.3, please open a new bug report. glusterfs-3.7.3 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user