Description of problem: in marker_readdirp_cbk inode_path is being called on the inodes that are not yet linked to the inode table. If glusterfs was built with DDEBUG, then it leads to process being asserted. Otherwise, building loc for xattr operation fails and might cause problems. list_for_each_entry (entry, &entries->list, list) { if ((strcmp (entry->d_name, ".") == 0) || (strcmp (entry->d_name, "..") == 0)) continue; ret = marker_inode_loc_fill (entry->inode, entry->d_name, &loc); if (ret) { gf_log (this->name, GF_LOG_WARNING, "Couln't build " "loc for %s/%s", uuid_utoa (local->loc.inode->gfid), entry->d_name); continue; } mq_xattr_state (this, &loc, entry->dict, entry->d_stat); loc_wipe (&loc); } Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/9320 (features/marker: do not call inode_path on the inode not yet linked) posted (#1) for review on master by Raghavendra Bhat (raghavendra)
*** Bug 1182514 has been marked as a duplicate of this bug. ***
REVIEW: http://review.gluster.org/9320 (features/marker: do not call inode_path on the inode not yet linked) posted (#2) for review on master by Raghavendra Bhat (raghavendra)
*** Bug 1174247 has been marked as a duplicate of this bug. ***
COMMIT: http://review.gluster.org/9320 committed in master by Raghavendra G (rgowdapp) ------ commit becdb76238c45ebe3edc967376f4aee87c0cb6e3 Author: Raghavendra Bhat <raghavendra> Date: Sun Dec 21 22:01:03 2014 +0530 features/marker: do not call inode_path on the inode not yet linked * in readdirp callbak marker is calling inode_path on the inodes that are not yet linked to the inode table. Change-Id: I7f5db29c6a7e778272044f60f8e73c60574df3a9 BUG: 1176393 Signed-off-by: Raghavendra Bhat <raghavendra> Reviewed-on: http://review.gluster.org/9320 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Raghavendra G <rgowdapp> Tested-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.0, please open a new bug report. glusterfs-3.7.0 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/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user