glusterfs.git, branch release-3.10

glusterd/ganesha : Skip non-ganesha nodes properly for ganesha HA set up

2018-04-30T07:21:27+00:00

Change-Id: Iff7bc3ead43e97847219c5a5cc8b967bf0967903
BUG: 1573078
Signed-off-by: Jiffin Tony Thottan

doc: Added release notes for 3.10.12

2018-04-24T13:49:38+00:00

fixes: bz#1553989

Change-Id: Iae1aa9ba71d1425a7797a84c937f2c4e760a4816
Signed-off-by: ShyamsundarR

server/auth: add option for strict authentication

2018-04-24T12:49:02+00:00

When this option is enabled, we will check for a matching
username and password, if not found then the connection will
be rejected. This also does a checksum validation of volfile

The option is invalid when SSL/TLS is in use, at which point
the SSL/TLS certificate user name is used to validate and
hence authorize the right user. This expects TLS allow rules
to be setup correctly rather than the default *.

This option is not settable, as a result this cannot be enabled
for volumes using the CLI. This is used with the shared storage
volume, to restrict access to the same in non-SSL/TLS environments
to the gluster peers only.

Tested:
  ./tests/bugs/protocol/bug-1321578.t
  ./tests/features/ssl-authz.t
  - Ran tests on volumes with and without strict auth
    checking (as brick vol file needed to be edited to test,
    or rather to enable the option)
  - Ran tests on volumes to ensure existing mounts are
    disconnected when we enable strict checking

Change-Id: I2ac4f0cfa5b59cc789cc5a265358389b04556b59
fixes: bz#1570428
Signed-off-by: Mohammed Rafi KC 
Signed-off-by: ShyamsundarR

shared storage: Prevent mounting shared storage from non-trusted client

2018-04-24T12:49:02+00:00

gluster shared storage is a volume used for internal storage for
various features including ganesha, geo-rep, snapshot.

So this volume should not be exposed to the client, as it is
a special volume for internal use.

This fix wont't generate non trusted volfile for shared storage volume.

Change-Id: I8ffe30ae99ec05196d75466210b84db311611a4c
updates: bz#1570428
Signed-off-by: Mohammed Rafi KC

libglusterfs: fix comparison of a NULL dict with a non-NULL dict

2018-04-19T09:03:52+00:00

Function are_dicts_equal() had a bug when the first argument was NULL and
the second one wasn't NULL. In this case it incorrectly returned that the
dicts were different when they could be equal.

Backport of:
> BUG: 1566732

BUG: 1569409
Change-Id: I0fc245c2e7d1395865a76405dbd05e5d34db3273
Signed-off-by: Xavi Hernandez

features/index: Choose different base file on EMLINK error

2018-04-10T13:39:23+00:00

Change-Id: I4648816af908539efdc2528608aa2ebf7f0d0e2f
fixes: bz#1553777
BUG: 1553777
Signed-off-by: Pranith Kumar K 
(cherry picked from commit bb12f2109a01856e8184e13cf984210d20155b13)

cluster/ec: send list-node-uuids request to all subvolumes

2018-04-05T15:35:51+00:00

The xattr trusted.glusterfs.list-node-uuids was only sent to a single
subvolume. This was returning null uuids from the other subvolumes as
if they were down.

This fix forces that xattr to be requested from all subvolumes.

Backport of:
> BUG: 1561406

Change-Id: If62eb39a6857258923ba625e153d4ad79018ea2f
BUG: 1561732
Signed-off-by: Xavi Hernandez

common-ha/scripts : pass the list of servers properly to stop_ganesha_all()

2018-04-04T04:05:00+00:00

Change-Id: I6d92623cd9fb450d7a27f5acc61eca0b3cbc9b08
BUG: 1563500
Signed-off-by: Jiffin Tony Thottan

gfapi : Resolve "." and ".." only for named lookups

2018-03-22T11:28:55+00:00

The patch https://review.gluster.org/#/c/17177 resolves "." and ".."
to corrosponding inodes and names before sending the request to the
backend server. But this will only work if inode and its parent is
linked properly. Incase of nameless lookup(applications like ganesha)
the inode of parent can be NULL(only gfid is send). So this patch will
resolve "." and ".." only if proper parent is available

Upstream reference
>Change-Id: I4c50258b0d896dabf000a547ab180b57df308a0b
>BUG: 1460514
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: https://review.gluster.org/17502
>Smoke: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>Reviewed-by: Poornima G 
>CentOS-regression: Gluster Build System 
>Reviewed-by: soumya k 
>Reviewed-by: Jeff Darcy 
>(cherry picked from commit a052b413242783f39cb3312a6a02bdd025b10f0c)

Change-Id: I4c50258b0d896dabf000a547ab180b57df308a0b
BUG: 1559352
Signed-off-by: Jiffin Tony Thottan

glusterd : introduce timer in mgmt_v3_lock

2018-03-20T13:58:38+00:00

Problem:
In a multinode environment, if two of the op-sm transactions
are initiated on one of the receiver nodes at the same time,
there might be a possibility that glusterd  may end up in
stale lock.

Solution:
During mgmt_v3_lock a registration is made to  gf_timer_call_after
which release the lock after certain period of time

>Change-Id: I16cc2e5186a2e8a5e35eca2468b031811e093843
>BUG: 1499004
>Signed-off-by: Gaurav Yadav 

Change-Id: I16cc2e5186a2e8a5e35eca2468b031811e093843
BUG: 1557304
Signed-off-by: Gaurav Yadav