From ea8d9ebafa4a6afb99721022e638292fd475ed62 Mon Sep 17 00:00:00 2001 From: Soumya Koduri Date: Mon, 30 Mar 2015 16:56:59 +0530 Subject: Upcall: Process each of the upcall events separately As suggested during the code-review of Bug1200262, have modified GF_CBK_UPCALL to be exlusively GF_CBK_CACHE_INVALIDATION. Thus, for any new upcall event, a new CBK procedure will be added. Also made changes to store upcall data separately based on the upcall event type received. BUG: 1217711 Change-Id: I0f5e53d6f5ece16aecb514a0a426dca40fa1c755 Signed-off-by: Soumya Koduri Reviewed-on: http://review.gluster.org/10049 Reviewed-by: Kaleb KEITHLEY Reviewed-on: http://review.gluster.org/10562 Tested-by: NetBSD Build System Tested-by: Gluster Build System --- api/src/glfs.c | 2 ++ 1 file changed, 2 insertions(+) (limited to 'api/src/glfs.c') diff --git a/api/src/glfs.c b/api/src/glfs.c index 12ca751e34d..23377f651d1 100644 --- a/api/src/glfs.c +++ b/api/src/glfs.c @@ -709,6 +709,8 @@ priv_glfs_free_from_ctx (struct glfs *fs) &fs->upcall_list, upcall_list) { list_del_init (&u_list->upcall_list); + GF_FREE (u_list->upcall_data.data); + GF_FREE (u_list); } (void) pthread_mutex_destroy (&fs->upcall_list_mutex); -- cgit