REVIEW: http://review.gluster.org/9941 (posix: handle failure from posix_resolve) posted (#1) for review on master by Vijaikumar Mallikarjuna (email@example.com)
REVIEW: http://review.gluster.org/9941 (posix: handle failure from posix_resolve) posted (#2) for review on master by Pranith Kumar Karampuri (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/9941 committed in master by Pranith Kumar Karampuri (email@example.com)
Author: vmallika <firstname.lastname@example.org>
Date: Thu Mar 19 07:02:24 2015 +0530
posix: handle failure from posix_resolve
When building ancestory, posix_resolve gets the inode
from the gfid. We need to handle the failure case from
Signed-off-by: vmallika <email@example.com>
Reviewed-by: Raghavendra Bhat <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Pranith Kumar Karampuri <firstname.lastname@example.org>
Tested-by: Pranith Kumar Karampuri <email@example.com>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.