glusterfs.git/xlators/features, branch v3.5.1beta

features/marker-quota: more stringent error handling in rename.

2014-05-11T02:36:10+00:00

If an error occurs and op_errno is not set to non-zero value, we can
end up in loosing a frame resulting in a hung syscall. This patch
adds code setting op_errno appropriately in storage/posix and
makes marker to set err to a default non-zero value in case of
op_errno being zero.

Change-Id: Idc2c3e843b932709a69b32ba67deb284547168f2
BUG: 833586
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.org/6913
Tested-by: Gluster Build System 
Reviewed-by: Niels de Vos

features/locks: Remove stale entrylk objects from 'blocked_locks' list

2014-05-08T13:00:56+00:00

        Backport of http://review.gluster.org/7560

* In the event of a DISCONNECT from a client, as part of cleanup,
  entrylk objects are not removed from the blocked_locks list before
  being unref'd and freed, causing the brick process to crash at
  some point when the (now) stale object is accessed again in the list.

* Also during cleanup, it is pointless to try and grant lock to a
  previously blocked entrylk (say L1) as part of releasing another
  conflicting lock (L2), (which is a side-effect of L1 not being
  deleted from blocked_locks list before grant_blocked_entry_locks()
  in cleanup) if L1 is also associated with the DISCONNECTing client.
  This patch fixes the problem.

Change-Id: Ie077f8eeb61c5505f047a8fdaac67db32e5d4270
BUG: 1089470
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/7576
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Reviewed-by: Niels de Vos

build: do not create versioned .so files

2014-05-05T13:35:38+00:00

There has been a misspelled option in the Makefile.am files. The option
is called -avoid-version, and not -avoidversion.

It is not trivial to provide a test-case for this. One way would be to
check generated RPMs with a command like this (output should be empty):

  $ rpm -qlp *.rpm | grep -E '/xlator/.+.so.0'

Change-Id: Ie1519455c9f9366feee0d3cafcc384b9eff57776
Reviewed-on-master: http://review.gluster.org/7299
BUG: 1078365
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/7301
Reviewed-by: Lalatendu Mohanty 
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY

features/locks: Remove stale inodelk objects from 'blocked_locks' list

2014-04-28T16:54:11+00:00

        Backport of  http://review.gluster.org/7512

* In the event of a DISCONNECT from a client, as part of cleanup,
  inodelk objects are not removed from the blocked_locks list before
  being unref'd and freed, causing the brick process to crash at
  some point when the (now) stale object is accessed again in the list.

* Also during cleanup, it is pointless to try and grant lock to a
  previously blocked inodelk (say L1) as part of releasing another
  conflicting lock (L2), (which is a side-effect of L1 not being
  deleted from blocked_locks list before grant_blocked_inode_locks()
  in cleanup) if L1 is also associated with the DISCONNECTing client.
  This patch fixes the problem.

Change-Id: I84d884e203761d0b071183860ffe8cae1f212ea5
BUG: 1089470
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/7575
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

features/locks: Fix a missing assignment in new_entrylk_lock()

2014-04-10T10:29:59+00:00

Change-Id: If5c03456d61ec930d588b57781fb545eed18e4a2
BUG: 1085220
Signed-off-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/7414
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra Bhat

locks: fix unconditional op_ret success of entrylk

2014-04-04T13:38:13+00:00

Bug introduced in recent refactoring. op_ret of entrylk() was always
getting set to 0 even though second locker wouldn't have gotten a lock.
This was resulting in multiple contenders to get locks granted at the
same time.

BUG: 849630
Change-Id: I130d521407afee15de59f270b59687d41982fb29
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/7232
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

features/glupy: Rename Glupy python module to avoid namespace conflict

2014-03-24T17:31:55+00:00

* Rename gluster.py to glupy.py to avoid namespace conflict (#1018619)
* Move the main Glupy files into glusterfs-extra-xlators rpm
* Move the Glupy Translator examples into glusterfs-devel rpm

Backport of: http://review.gluster.org/#/c/6979/

Change-Id: Ie9b71b56502f8e98c527ade381c918446bc7f022
BUG: 1018619
Signed-off-by: Justin Clift 
Reviewed-on: http://review.gluster.org/7316
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Jeff Darcy

features/quota: fix the dict leak when quota is off

2014-03-15T12:46:50+00:00

Change-Id: I15036da90e96b69858eac5a19bd438df3bd8cc53
BUG: 1075506
Signed-off-by: Varun Shastry 
Reviewed-on: http://review.gluster.org/7233
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

geo-rep/gfid-access: Fix errno for non-existent GFID.

2014-03-03T05:05:29+00:00

Because of http://review.gluster.org/#/c/6318/ patch,
ESTALE is returned for a lookukp on non-existent GFID.
But ENOENT is more appropriate when lookup happens
through virtual .gfid directory on aux-gfid-mount
point. This is avoids confusion for the consumers
of gfid-access-translator like geo-rep which expects
ENOENT.

Change-Id: I4add2edf5958bb59ce55d02726e6b3e801b101bb
BUG: 1069191
Signed-off-by: Kotresh H R 
Reviewed-on: http://review.gluster.org/7154
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra G 
Reviewed-by: Venky Shankar 
Reviewed-by: Anand Avati 
Reviewed-on: http://review.gluster.org/7163
Reviewed-by: Vijay Bellur

features/quota: fix crash in error handling after building ancestry.

2014-02-08T16:22:22+00:00

Change-Id: Ifbebf1aa496d49a6c4bb30258b83aaf9792828e5
BUG: 1059833
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.org/6924
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur