glusterfs.git/tests, branch v3.6.2beta1

tests: spurious failures fix for quota-anon-fd-nfs.t

2014-12-10T18:10:11+00:00

Change-Id: I4f7ee68c514d8d322e25cf74167f288a8b6f8164
BUG: 1165938
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/9108
Tested-by: Gluster Build System 
Reviewed-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/9148
Reviewed-by: Raghavendra Bhat 
Tested-by: Raghavendra Bhat

tests: regression test portability - quota-anon-fd-nfs.t

2014-12-10T06:19:38+00:00

Fix portability problems in quota-anon-fd-nfs.t
- Use mount_nfs wrapper and include nfs.rc to get it defined.
- umount NFS before cleanup to avvoid deadlocks.
- umount -l is Linux-specific, use umount -f on BSD.
- wait for 1s for portmap registration before mouting NFS.
- mount from $H0 instead of localhost: the later fails on NetBSD.
- Test quota without filling GB of data, 20MB is enough and it
  will be gentle with smaller setups.
- wait for write behind to complete before testing quota overflow

BUG: 1165938
Change-Id: I097d5faed2fa7b6438aaa56def85172f23bbe7dc
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.org/8969
Reviewed-by: Shyamsundar Ranganathan 
Reviewed-by: Niels de Vos 
Tested-by: Kiran Patil 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/8997
Reviewed-by: Raghavendra Bhat 
Tested-by: Raghavendra Bhat

protocol/server: No root-squash checks for self-heal pid

2014-12-10T06:17:58+00:00

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

Problem:
Self-heal pid used to be -1 which was colliding with gsyncd. Gsyncd
was not checked for root-squash authentication. Recently self-heal
pid changed to -6, but root-squash authentication is not disabled
for this.

Fix:
disable root-squash authentication for self-heal

Change-Id: I594a732d800902ce805f849813631da36d8d3dc7
BUG: 1170514
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/9234
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra Bhat 
Tested-by: Raghavendra Bhat

tests: spurious failure fix in mgmt_v3_locks.t

2014-11-30T07:29:26+00:00

Change-Id: I7c4599648b5d47d93a447e58c063fab21e8f9ef7
BUG: 1165938
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/9114
Tested-by: Gluster Build System 
Reviewed-by: Kaushal M 
Tested-by: Kaushal M 
Reviewed-on: http://review.gluster.org/9149
Reviewed-by: Raghavendra Bhat

features/marker: Filter internal xattrs in lookup

2014-11-17T07:35:25+00:00

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

Afr should ignore quota-size-key as part of self-heal
but should heal quota-limit key.

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

glupy: portability fixes

2014-11-17T07:06:25+00:00

Fixes portability problems so that NetBSD passes tests/features/glupy.t

- Use python-config to detect python build environment on all systems,
  not just Linux and Darwin.
- Get the site-package directory from python and make sure we install
  glupy.py there, Previously we installed within glusterfs prefix,
  which caused a problem if it was different that python's prefix.
- Set PYTHONPATH for tests so that the detected site-packages is used
  in python's search path. This should be useless, but let us have it
  just in case.
- Pass glupy.so path from glusterfsd to glupy.py through an
  environment variable and use it in CDLL instead of "", as the
  later seems not portable (at least it fails on NetBSD).
- Use gil_init_key pthread_getspecific to avoid deadlocks (that
  code was #ifdef out, perhaps because it was not needed on Linux,
  but it seems to be required for NetBSD.
- Recover the error message from Python and send it to the logs
  to help debugging problems.

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

This is the same patchset as previously submitted to retrigger regression
tests after a spurious failure.

BUG: 1138897
Change-Id: I1e23ba5cc18f129ee1032f905cb053953b683a81
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.org/8980
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

Use C-locale for numeric/string conversion routines

2014-11-17T06:55:45+00:00

(strtod, ...) or config file parsing might fail.

Cherry picked from commit 5b8de971a4b81bc2bd6de0ffc6386587226295c6:
> Change-Id: I649f29bbf87222399a0c2d1ed5a3bf136c613b9b
> BUG: 1117951
> Signed-off-by: Anders Blomdell 
> Reviewed-on: http://review.gluster.org/8299
> Tested-by: Gluster Build System 
> Reviewed-by: Prashanth Pai 
> Reviewed-by: Vijay Bellur 

Change-Id: I649f29bbf87222399a0c2d1ed5a3bf136c613b9b
BUG: 1157107
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/9132
Tested-by: Gluster Build System 
Reviewed-by: Humble Devassy Chirammal 
Reviewed-by: Vijay Bellur

ec: Correctly handle quota xattrs

2014-11-15T18:01:14+00:00

This is a backport of http://review.gluster.org/8990/

Change-Id: I35e11d83c318210d44b918e847cf13db35b01510
BUG: 1158088
Signed-off-by: Xavier Hernandez 
Reviewed-on: http://review.gluster.org/8992
Tested-by: Gluster Build System 
Reviewed-by: Dan Lambright

features/snapview-server: check if the reference to the snapshot world is correct before doing any fop

2014-10-30T18:39:15+00:00

The following operations might lead to problems:
* Create a file on the glusterfs mount point
* Create a snapshot (say "snap1")
* Access the contents of the snapshot
* Delete the file from the mount point
* Delete the snapshot "snap1"
* Create a new snapshot "snap1"

Now accessing the new snapshot "snap1" gives problems. Because the inode and
dentry created for snap1 would not be deleted upon the deletion of the snapshot
(as deletion of snapshot is a gluster cli operation, not a fop). So next time
upon creation of a new snap with same name, the previous inode and dentry itself
will be used. But the inode context contains old information about the glfs_t
instance and the handle in the gfapi world. Directly accessing them without
proper check leads to ENOTCONN errors. Thus the glfs_t instance should be
checked before accessing. If its wrong, then right instance should be obtained
by doing the lookup.

Change-Id: I975245b8f6b7fea0a90eb5e36e8149d12457ac10
BUG: 1158791
Reviewed-on: http://review.gluster.org/9007
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

socket: disallow CBC cipher modes

2014-10-29T11:37:55+00:00

This is related to CVE-2014-3566 a.k.a. POODLE.

	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3566

POODLE is specific to CBC cipher modes in SSLv3.  Because there is no
way to prevent SSLv3 fallback on a system with an unpatched version of
OpenSSL, users of such systems can only be protected by disallowing CBC
modes.  The default cipher-mode specification in our code has been
changed accordingly.  Users can still set their own cipher modes if they
wish.  To support them, the ssl-authz.t test script provides an example
of how to combine the CBC exclusion with other criteria in a script.

Change-Id: Ib1fa547082fbb7de9df94ffd182b1800d6e354e5
BUG: 1157659
Signed-off-by: Jeff Darcy 
Reviewed-on: http://review.gluster.org/8962
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/8987
Reviewed-by: Niels de Vos 
Tested-by: Niels de Vos