REVIEW: http://review.gluster.org/14181 (gfapi/upcall: Ignore handle create failures) posted (#1) for review on release-3.7 by soumya k (skoduri)
COMMIT: http://review.gluster.org/14181 committed in release-3.7 by Kaleb KEITHLEY (kkeithle) ------ commit 9abed2198f78e476fff2c8cca3307915852043fe Author: Soumya Koduri <skoduri> Date: Sat Apr 30 22:01:47 2016 +0530 gfapi/upcall: Ignore handle create failures In "glfs_h_poll_cache_invalidation", we need to send upcall only if there is a corresponding inode entry in the gfapi inode table for that handle. That's because the application will have reference to the inode as long as it operates on any handle. That means the only case in which we cannot find inode is when the application has closed the handle (either as part of unlink or for any other purpose). But since it will have no more references and will not be interested in any upcall event for that handle, we can safely ignore such cases. Note: This will affect only that particular applicaiton process/local libgfapi client. This is backport of the below mainline fix - http://review.gluster.org/14132 Change-Id: I9499cd9c284350d4a271e58f2a0966db65a7a61c BUG: 1332433 Signed-off-by: Soumya Koduri <skoduri> Reviewed-on: http://review.gluster.org/14132 Reviewed-by: jiffin tony Thottan <jthottan> Reviewed-by: Kaleb KEITHLEY <kkeithle> Reviewed-on: http://review.gluster.org/14181 NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Smoke: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/14524 (gfapi/upcall : remove unused variable ret in glfs_h_find_handle) posted (#1) for review on master by jiffin tony Thottan (jthottan)
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.12, please open a new bug report. glusterfs-3.7.12 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] https://www.gluster.org/pipermail/gluster-devel/2016-June/049918.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user