REVIEW: http://review.gluster.org/13987 (inode: Always fetch first entry from the inode lists during inode_table_destroy) posted (#1) for review on master by soumya k (email@example.com)
COMMIT: http://review.gluster.org/13987 committed in master by Jeff Darcy (firstname.lastname@example.org)
Author: Soumya Koduri <email@example.com>
Date: Wed Apr 13 12:50:49 2016 +0530
inode: Always fetch first entry from the inode lists during inode_table_destroy
In inode_table_destroy, we iterate through lru and active lists
to move the entries to purge list so that they can be destroyed
But if used "list_for_each_entry" or "list_for_each_entry_safe"
to iterate, we could end up accessing the entries which may have
got moved to different(purge) lists in the process and can result
in either infinite loop or crash. The safe approach seems to fetch
the first entry of the list in each iteration till it gets empty.
Signed-off-by: Soumya Koduri <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
NetBSD-regression: NetBSD Build System <firstname.lastname@example.org>
CentOS-regression: Gluster Build System <email@example.com>
Reviewed-by: Kaleb KEITHLEY <firstname.lastname@example.org>
Reviewed-by: Niels de Vos <email@example.com>
Reviewed-by: Jeff Darcy <firstname.lastname@example.org>
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.8.0, please open a new bug report.
glusterfs-3.8.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.