glusterfs.git, branch v3.4.0qa8

cluster/dht: stack wind with cookie

2013-02-01T01:18:03+00:00

Default_fops uses stack_wind_tail. It winds without creating the frame leading
into wrong subvol return in the cookie. To avoid the problem caused by the
same, we're getting the subvol by passing the cookie.

Change-Id: I51ee79b22c89e4fb0b89e9a0bc3ac96c5b469f8f
BUG: 893338
Signed-off-by: Varun Shastry 
Reviewed-on: http://review.gluster.org/4388
Reviewed-by: Jeff Darcy 
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati 
Tested-by: Anand Avati

fuse-bridge: fix some breakages from lock migration patch

2013-01-31T07:43:49+00:00

- do not attempt lock migration if no locks were ever acquired on
  an fd.

- fix fd_lk_ctx_t ref leak during fd migration

- remove spurious fd_unref() (probably added to compensate for
  the fd_ref leak in syncop_open_cbk)

- remove @newfdptr out-param which makes fd ref management really
  tricky (and currently refs were unmanaged for the out-param).
  Instead acquire ref and unref within lock migration function.

Change-Id: I4cc9c451f0df4c051612bd1fa7bef11e801570e4
BUG: 808400
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/4453
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra Bhat

fd-lk: implement new method to check for empty fd_lk_ctx_t

2013-01-31T07:41:16+00:00

to use this in fuse-bridge, to conditionally attempt lock migration
to new graph.

Change-Id: I9b10d5839c4ac6051c75e4c020371391cd886ac8
BUG: 808400
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/4455
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra Bhat

libglusterfs/syncop: do not hold ref on the fd in cbk

2013-01-31T07:40:37+00:00

* Do not do fd_ref in cbks of the fops which return a fd (such as
  open, opendir, create).

Change-Id: Ic2f5b234c5c09c258494f4fb5d600a64813823ad
BUG: 885008
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.org/4282
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Anand Avati

762989.t: fix a typo by grepping only the blocked port number from netstat o/p

2013-01-30T18:40:41+00:00

Change-Id: I14c3daa799f0936014bf8aa9fd798ecbaec6e912
BUG: 762989
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.org/4426
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

glusterfs : Moved option files, and statedumps from /tmp

2013-01-29T23:27:29+00:00

Change-Id: Ibdede396c4d6859225937316b7a59a661bcaf9f5
BUG: 764890
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/4422
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

cluster/afr: if a subvolume is down wind the lock request to next

2013-01-29T20:50:55+00:00

When one of the subvolume is down, then lock request is not attempted
on that subvolume and move on to the next subvolume.

/* skip over children that are down */
                while ((child_index < priv->child_count)
                       && !local->child_up[child_index])
                        child_index++;

In the above case if there are 2 subvolumes and 2nd subvolume is down (subvolume
1 from afr's view), then after attempting lock on 1st child (i.e subvolume 0)
child index is calculated to be 1. But since the 2nd child is down child_index
is incremented to 2 as per the above logic and lock request is STACK_WINDed to
the child with child_index 2. Since there are only 2 children for afr the child
(i.e the xlator_t pointer) for child_index will be NULL. The process crashes
when it dereference the NULL xlator object.

Change-Id: Icd9b5ad28bac1b805e6e80d53c12d296526bedf5
BUG: 765564
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.org/4438
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

Tests: Test functionality of flush/fsync with afr

2013-01-29T20:34:16+00:00

Change-Id: I307a77e90e1852f5e43d50e347f7b52468105389
BUG: 888174
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/4447
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

cluster/afr: wakeup delayed post op on fsync

2013-01-29T20:33:05+00:00

Change-Id: I5d84ef72615f9d71b4af210976e2449de6e02326
BUG: 888174
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/4446
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

cluster/afr: Change order of unwind, resume for writev

2013-01-29T20:29:51+00:00

Generally inode-write fops do transaction.unwind then
transaction.resume, but writev needs to make sure that
delayed post-op frame is placed in fdctx before unwind
happens. This prevents the race of flush doing the
changelog wakeup first in fuse thread and then this
writev placing its delayed post-op frame in fdctx.
This helps flush make sure all the delayed post-ops are
completed.

Change-Id: Ia78ca556f69cab3073c21172bb15f34ff8c3f4be
BUG: 888174
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/4428
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati