glusterfs.git/xlators/mount, branch v3.3.0qa39

mount/fuse: unref the fds after they have been migrated to the new graph

2012-04-24T20:08:24+00:00

In fuse upon graph changes fds were being migrated to the new graph.
It was done by taking all the fds from the fdtable in a structure and then
migrating each fd in the structure to the new graph. But after the fds
are migrated the structure which had the fds within it (that is refed fds)
was being freed without unrefing the fds, thus leading to a fd leak.

Change-Id: I7b25220a48954384a004373d378cee11c6109f7e
BUG: 811552
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.com/3222
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

NetBSD build fixes

2012-04-24T04:29:03+00:00

Signed-off-by: Emmanuel Dreyfus 

Change-Id: I8f9aabeadd2f842521a82e59594115bd80155d68
BUG: 2923
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.com/3053
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

core: coverity issues fixed

2012-04-23T21:52:57+00:00

this is not a complete set of issues getting fixed. Will
address other issues in another patch.

Change-Id: Ib01c7b11b205078cc4d0b3f11610751e32d14b69
Signed-off-by: Amar Tumballi 
BUG: 789278
Reviewed-on: http://review.gluster.com/3145
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy

clean up handling of special client pids

2012-04-23T21:50:55+00:00

- no need to name a lower boundary [drop GF_CLIENT_PID_MIN]
- drop utility function to decide about pid speciality [gf_pid_client_check()];
  when we implement uniform policy for special pids, use just comparison with
  GF_CLIENT_PID_MAX (currently such uniform policy exists in io-threads, where
  special clients get lowest priority)
- io-threads: drop numeric literal, use GF_CLIENT_PID_MAX
- xattr flipping (in fuse):
  - fuse_xattr_alloc_default() made static
  - avoid compiler warnings wrt. partial enum traversal in the switch
    by not casting the original numeric value to gf_client_pid_t (enum) type
  - trim down the switch to those cases with which there is something to do
    [GF_CLIENT_PID_GSYNCD, GF_CLIENT_PID_HADOOP]
  - eliminate the (theoretical) chance of succesfully returning
    from fuse_flip_xattr_ns() with unallocated nkey
    [as was the case with pids GF_CLIENT_PID_{MIN,MAX,DEFRAG}]

Change-Id: Ic2b83b908d8e3be23a7fba1e5895869828a6194b
BUG: 765433
Signed-off-by: Csaba Henk 
Reviewed-on: http://review.gluster.com/3170
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-by: Anand Avati

fuse: allow requests during mount (needed for SELinux labels)

2012-04-23T21:37:24+00:00

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

glusterd/rebalance: Start process with xlator option client-pid -3

2012-04-16T18:21:50+00:00

This would prevent updation of xtime by the marker.

Signed-off-by: shishir gowda 
Change-Id: I11e287511026326271c2926e55993e48b32018f6
BUG: 812287
Reviewed-on: http://review.gluster.com/3144
Tested-by: Gluster Build System 
Reviewed-by: Mohammed Junaid 
Reviewed-by: Csaba Henk 
Reviewed-by: Vijay Bellur

mount.glusterfs: multiple fixes

2012-04-13T07:20:04+00:00

* noticed that the regex to parse the options were not fool proof.
  for example, 'ro' in a logfilename could have made the mount
  point read-only. Now fixed.

* this issue existed for 'acl', 'worm' options.

* log-server/log-server-port options were legacy, and no more
  needed in codebase.

* refactored option processing in general to avoid above issues

Change-Id: I172d24c86ece9a34420ba997fa385e304b4924ae
BUG: 806978
Signed-off-by: Jeff Darcy 
Reviewed-on: http://review.gluster.com/3058
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

fuse-bridge: generate GFID as gfid-req in fresh lookup

2012-04-11T16:55:03+00:00

This is necessary for self-heal to assign fresh GFID when
performing lookup on files/dirs without GFID (migration from
old version, etc.)

Change-Id: I6f070255dc6e85bf6625b704cb5fb7f831ee58e6
BUG: 795355
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.com/3101
Tested-by: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri

fuse-bridge/fd-migration: document migration failures in fdctx.

2012-04-04T23:27:45+00:00

Change-Id: Ib85871e586f89f88dd7bf738fbb284b5d7b70a86
BUG: 809919
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.com/3085
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

core: adding extra data for fops

2012-03-22T23:40:27+00:00

with this change, the xlator APIs will have a dictionary as extra
argument, which is passed between all the layers. This can be
utilized for overloading in some of the operations.

Change-Id: I58a8186b3ef647650280e63f3e5e9b9de7827b40
Signed-off-by: Amar Tumballi 
BUG: 782265
Reviewed-on: http://review.gluster.com/2960
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati