GLUSTER handle_release will signal SIGSEGV, Segmentation fault.

[JYang1986]

in this commit
b0a492a

static void handle_release(struct fsal_obj_handle *obj_hdl)
{
......

	fsal_obj_handle_fini(&objhandle->handle, true);

	if (obj_hdl->type == REGULAR_FILE) {
		fsal_status_t st;

		st = close_fsal_fd(obj_hdl, &my_fd->fsal_fd,
				   false);

		if (FSAL_IS_ERROR(st)) {
			LogCrit(COMPONENT_FSAL,
				"Could not close hdl 0x%p, status %s error %s(%d)",
				obj_hdl, fsal_err_txt(st),
				strerror(st.minor), st.minor);
		}
	}
.....
	if (objhandle->handle.type == REGULAR_FILE)
		destroy_fsal_fd(&my_fd->fsal_fd);

	gsh_free(objhandle);

#ifdef GLTIMING
	now(&e_time);
	latency_update(&s_time, &e_time, lat_handle_release);
#endif
} 

fsal_obj_handle_fini will memset(&obj->obj_ops, 0, sizeof(obj->obj_ops)) obj->obj_ops=NULL
then close_fsal_fd will use obj->obj_ops then SIGSEGV

could move fsal_obj_handle_fini(&objhandle->handle, true); like this is ok？

	if (objhandle->handle.type == REGULAR_FILE)
		destroy_fsal_fd(&my_fd->fsal_fd);
       fsal_obj_handle_fini(&objhandle->handle, true);
	gsh_free(objhandle);

[ffilz]

Please submit a patch via Gerrithub (see src/CONTRIBUTING_HOWTO.txt).