Hide Forgot
It was seen earlier and seen now too (with bug 761853). Need to fix this by having a range check inside inode_path().
PATCH: http://patches.gluster.com/patch/742 in master (break inode_path if the length of the path crosses PATH_MAX)
PATCH: http://patches.gluster.com/patch/765 in release-2.0 (break inode_path if the length of the path crosses PATH_MAX)