glusterfs.git/libglusterfs, branch v3.2.7qa1

libglusterfs: Destroy stack_lock in STACK_DESTROY

2012-03-18T07:53:25+00:00

Change-Id: Icf910a899db136061a439a2e5e0951da55b92c00
BUG: 798907
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.com/2902
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

core/stack: perform locked winds

2012-01-11T08:18:22+00:00

In configurations like pump, where there is a cluster translator on
top of io-threads, there are situations where two concurrent stack-winds
can be performed on the same call stack in multiple threads. This patch
holds locks during the call frame list manipulation

Change-Id: I51539210dc8101f7a80cf9bc103b5eff0c86dc9f
BUG: 765522
Reviewed-on: http://review.gluster.com/2629
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

stripe read: Wipe stat in reply to prevent truncated error.

2011-11-09T06:11:48+00:00

If the read request, does not fall to the subvolume with the largest
file size set, then we never return the correct size. This leads to
clients seeing a truncated file error.

The work around is to wipe stat being returned as part of read call.

Change-Id: I4e76d09d7919fd0be616fe140e08f89a0dbcc444
BUG: 3774
Reviewed-on: http://review.gluster.com/682
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

libglusterfs: copy the gfid in entry_copy

2011-11-04T15:55:54+00:00

Change-Id: I8a43b5fbe7a90344f490090df853d47b651bc0ff
BUG: 3760
Reviewed-on: http://review.gluster.com/672
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

libglusterfs: fork'ed children should start with an empty signal mask.

2011-11-04T09:06:25+00:00

Fork'ing causes child to inherit the signal mask of the parent. Hence
executables invoked from glusterd will inherit glusterd's signal mask.
Thus, utilities like gsyncd will have some signals (SIG{USR1,USR2,..})
masked, which are needed for gsyncd log-rotate command to function
properly.

Change-Id: Id66d185c8497cd8947f32769fa7ea62dc34e1100
BUG: 2787
Reviewed-on: http://review.gluster.com/657
Tested-by: Gluster Build System 
Reviewed-by: Csaba Henk 
Reviewed-by: Vijay Bellur

pump: Change crawl to accommodate afr_lookup changes

2011-10-28T11:54:08+00:00

Change-Id: I895574dd6fa411784eb5282c799ccf3ff7c65625
BUG: 3747
Reviewed-on: http://review.gluster.com/635
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

check the return value of inode_path for less than or equal to zero

2011-10-28T11:14:56+00:00

Change-Id: I9bbdfe79664c1339b66819a6c7ea4b7698beb5c6
BUG: 3757
Reviewed-on: http://review.gluster.com/640
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

core: build warning fixes

2011-10-24T05:46:56+00:00

the current way is very crude method to solve the warning issues with
gcc 4.6.1+ versions. Actual fix is to go through each of such warnings
and fix individually.

added a TODO to remove the 'pragma' once we fix the root cause of
warnings. till then this patch is work around to shift the build
system.

Change-Id: Icffc427b1d736e719e15f40e1dd89330ea395c40
BUG: 2550
Reviewed-on: http://review.gluster.com/625
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-by: Vijay Bellur

storage/posix: posix changes to handle gfid/conflicts self-heal

2011-10-19T09:28:25+00:00

Change-Id: Ib759befe1800bc6fd93bdf44f3a7f89bfffff46e
BUG: 3734
Reviewed-on: http://review.gluster.com/612
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

libglusterfs/syncop: do not rely on synctask set in makecontext

2011-10-10T11:03:55+00:00

Across glibc implementations, interpretation of argc/argv passed
to makecontext() is different. This patch does away with dependence
on such arguments passed to makecontext(). Instead,synctask reference
is retrieved from pthread_getspecific().

Change-Id: Ib00924ddb115877c643818e22afa8941eceaff76
BUG: 3636
Reviewed-on: http://review.gluster.com/571
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur