glusterfs.git, branch v3.3.0qa31

protocol/client: memory leak fixes.

2012-03-21T05:37:18+00:00

Signed-off-by: Raghavendra G 
Change-Id: I804c934d79ed13ded9d1b741cef6597bc238e476
BUG: 803675
Reviewed-on: http://review.gluster.com/2987
Reviewed-by: Amar Tumballi 
Tested-by: Gluster Build System

performance/read-ahead: destroy pages which survived from being flushed

2012-03-20T17:42:42+00:00

in flush_region because of frames waiting on them, after those frames
are served.

Change-Id: Ic8402f3da32058a1a11e62124b598b0ec3befeff
BUG: 767948
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.com/2982
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-by: Vijay Bellur

performance/io-cache: destroy the pages which survived in

2012-03-20T16:48:58+00:00

__ioc_page_destroy because of non NULL waitq in ioc_fault_cbk.

Change-Id: I00b83f8bf0a654b3a3a23cf0b25657fbfda17804
BUG: 767948
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.com/2981
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-by: Vijay Bellur

protocol/server: remove the transport from the list irrespective of lock-heal is on/off

2012-03-20T14:49:01+00:00

Upon getting disconnect, remove the transport from the list of transports that
protocol server maintains irrespective of whether lock-heal is on or off, since
upon reconnect a new transport would be created.

Change-Id: I18a269a93487d6e2cb11c345b6dde813d089809c
BUG: 803815
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.com/2980
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

features/marker: Replacing -1 with GF_CLIENT_PID_GSYNCD as part of code cleanup.

2012-03-20T14:47:21+00:00

Change-Id: Ia665060bff636b372904a726aba5249de9ade124
BUG: 769494
Signed-off-by: Mohammed Junaid 
Reviewed-on: http://review.gluster.com/2971
Tested-by: Gluster Build System 
Reviewed-by: Csaba Henk

replicate: fix a glitch in up_count/down_count updates.

2012-03-19T22:19:50+00:00

Change-Id: I4919a98191bf7fe5edad9a149a129bcd177cd4a8
BUG: 802522
Signed-off-by: Jeff Darcy 
Reviewed-on: http://review.gluster.com/2927
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

protocol/client: Handle failures in lock self healing gracefully (part2).

2012-03-19T16:16:23+00:00

During reopening of fd's and reacquiring of locks on the fd (after a
reconnect), a release on a fd on which reacquiring of locks is in progress
will free up fdctx. This patch will keep fdctx valid until the reacquiring
of locks is in progress.

Change-Id: I0fae27544a7f8ddaa26def4ee4d41a8a2b322521
BUG: 795386
Signed-off-by: Mohammed Junaid 
Reviewed-on: http://review.gluster.com/2819
Reviewed-by: Amar Tumballi 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

rpc-clnt: separate out connection_cleanup() from destroy()

2012-03-19T16:14:40+00:00

noticed that there are possibilities where one would like to do a
connection_cleanup() before destroying a RPC connection itself, also
current code is such that, rpc_clnt_connection_cleanup() does
rpc_clnt_ref() and unref(), creating a race window/double unref
possibilities in the code.

by separating out the functions, this race window/double fault can be
prevented.

Change-Id: I7ebd3392efa891232857b6db9108b0b19e40fc12
Signed-off-by: Amar Tumballi 
BUG: 802403
Reviewed-on: http://review.gluster.com/2979
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

protocol/client: Handle failures in lock self healing gracefully (part 1).

2012-03-19T16:05:58+00:00

During reopening of fd's and reacquiring of locks on the fd (after a
reconnect), a release on a fd on which reacquiring of locks is in progress
will free up fdctx. This patch will keep fdctx valid until the reacquiring
of locks is in progress.

Change-Id: I0464c751a5aa986abac0b72b48b261fceeba24e8
BUG: 795386
Signed-off-by: Mohammed Junaid 
Reviewed-on: http://review.gluster.com/2937
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

protocol/server: Handle server send reply failure gracefully.

2012-03-19T15:11:43+00:00

Server send reply failure should not call server connection cleanup because
if a reconnection happens with in the grace-timeout the connection object is
reused. We must cleanup only on grace-timeout.

Change-Id: I7d171a863382646ff392031c2b845fe4f0d3d5dc
BUG: 803365
Signed-off-by: Mohammed Junaid 
Reviewed-on: http://review.gluster.com/2947
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur