summaryrefslogtreecommitdiffstats
path: root/tests/cluster.rc
diff options
context:
space:
mode:
authorAnand Avati <avati@redhat.com>2013-09-03 15:18:26 -0700
committerVijay Bellur <vbellur@redhat.com>2013-09-05 05:24:42 -0700
commit4b317e64cafe1e8621a8b24ebb8243931cda264a (patch)
tree308bec11ba321159b385693077301fdcffe13ca9 /tests/cluster.rc
parent774e6d162dd826be6357de6112bac5a345790a9e (diff)
glusterfs, gfapi: fix symbol clash
The callback structures in both protocol/client and glusterfsd, gfapi used the same name for the actor table - gluster_cbk_actors. CBKs are required only for the management connection, and the actors of protocol/client are NOP functions. This supposed-to-be NOP function dispatch tabble is actually ending up pointing to the actor table of glusterfsd or gfapi. These functions, even though set wrongly, are not even expected to be called through the protocol/client callback path. Glusterd however sends the FETCHSPEC (and other) notify callbacks to *all* connected clients unconditionally, and there is a small period of time when protocol/client is connected to glusterd for PORTMAP query. If the FETCHSPEC callback notify is issued in this window of time, we end up calling the wrong actor in the client side resulting in a crash. Change-Id: I605ff7df64c7faf4607369bbf275aedec28e1778 BUG: 1004091 Signed-off-by: Anand Avati <avati@redhat.com> Reviewed-on: http://review.gluster.org/5767 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Amar Tumballi <amarts@redhat.com>
Diffstat (limited to 'tests/cluster.rc')
0 files changed, 0 insertions, 0 deletions