glusterfs.git, branch v3.5.2

Release Notes for GlusterFS 3.5.2

2014-07-31T10:56:18+00:00

BUG: 1104511
Change-Id: I4b9bb636c1b07fc3552785e3b4ba277fd2301ed5
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/8339
Reviewed-by: Lalatendu Mohanty 
Reviewed-by: Humble Devassy Chirammal

gfapi: In glfs_set_volfile_server() remove the port number check.

2014-07-31T07:50:47+00:00

The documentation for glfs_set_volfile_server() api says that the
port zero is a valid value. Specifying 0 uses the default port
number GF_DEFAULT_BASE_PORT. Hence removing the check for port being
zero.

Master branch commit 6567d141c1b0112acb35e711371ae5a879fc645a:
> Change-Id: I942a7fe54a418231a438ab67756537df8f28d2de
> BUG: 1084964
> Signed-off-by: Poornima G 
> Reviewed-on: http://review.gluster.org/7409
> Reviewed-by: Raghavendra Talur 
> Reviewed-by: Krishnan Parthasarathi 
> Tested-by: Gluster Build System 
> Reviewed-by: Vijay Bellur 

Change-Id: I942a7fe54a418231a438ab67756537df8f28d2de
BUG: 1124728
Signed-off-by: Poornima G 
Reviewed-on: http://review.gluster.org/8374
Reviewed-by: Niels de Vos 
Tested-by: Gluster Build System

cli: Fix xml output for volume status

2014-07-21T07:11:19+00:00

The XML output for volume status was malformed when one of the nodes is
down, leading to outputs like
-------
          
             
               NFS Server
               localhost
               63ca3d2f-8c1f-4b84-b797-b4baddab81fb
               1
               2049
               2130
             
-----

This was happening because we were starting the  element before
determining if node was present, and were not closing it or clearing it
when not finding the node in the dict.

To fix this, the  element is only started once a node has been
found in the dict.

Cherry picked from commit 2ba42d07eb967472227eb0a93e4ca2cac7a197b5:
> Change-Id: I6b6205f14b27a69adb95d85db7b48999aa48d400
> BUG: 1046020
> Signed-off-by: Kaushal M 
> Reviewed-on: http://review.gluster.org/6571
> Reviewed-by: Aravinda VK 
> Reviewed-by: Krishnan Parthasarathi 
> Tested-by: Gluster Build System 
> Reviewed-by: Vijay Bellur 

Change-Id: I6b6205f14b27a69adb95d85db7b48999aa48d400
BUG: 1117241
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/8334
Tested-by: Gluster Build System 
Reviewed-by: Kaushal M

heal: fix the way we check the presence of AFR in glfsheal

2014-07-18T16:18:14+00:00

Problem:
glfsh_validate_replicate_volume() used to check if AFR was the parent of
all client xlators present in the graph. This need not always be true, for
example, for user-serviceable-snapshots where the parent of snapd-client is
snapview-client.

Fix:
glfsh_validate_replicate_volume() returns true if atleast one client
xlator has AFR as its parent. Also, AFR need not be its immediate
parent, but be present somewhere in its parent ancestry.

Change-Id: Id37ac88c3202bb2fdcae56e108adc461dc8a9a37
BUG: 1115950
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/8229
Tested-by: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri 
Reviewed-by: Niels de Vos

cluster/afr: Fix leaks in self-heal code path

2014-07-18T10:28:22+00:00

Change-Id: I5301ec9ebac27afe52e85cad75e6395d7f891355
BUG: 1120151
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/8316
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi 
Reviewed-by: Ravishankar N 
Reviewed-by: Niels de Vos

build: glusterfs.spec.in, adding nfs-utils package dependency for server package

2014-07-15T15:46:31+00:00

nfs-utils provides rpc.statd and it is a requirement for gluster-nfs

Master review:    http://review.gluster.org/7966
Master commit-Id: c34850ec71c9d6a4f30ad2e5e96aa15bc8a87064

Change-Id: I054b7d6d8fb1efe0fed9c90077a93c4f559c1ef4
BUG: 1113007
Reported-by: Satheesaran Sundaramoorthi 
Reviewed-by: Niels de Vos 
Signed-off-by: Vikhyat Umrao 
Reviewed-on: http://review.gluster.org/8172
Tested-by: Gluster Build System

client_t: Fix memory leaks

2014-07-14T09:38:19+00:00

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

- Assign frame->root->client so that gf_client_unref happens
  in server_connection_cleanup_flush_cbk
- Avoid taking extra ref in gf_client_get

TODO:
The whole reason why there are two types of refs
bind, ref-count is to avoid lock inside lock which
is not the case now. I will be sending one more patch
which will accomplish that as well as changing the
tablearray to list

BUG: 1116672
Change-Id: Ica87b9cbf02cae34c10789cfb56d1ccdc393cbf0
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/8289
Tested-by: Gluster Build System 
Reviewed-by: Niels de Vos

protocol/server: '/s/ESTALE/ENOENT' only in lookup path

2014-07-14T09:22:14+00:00

Problem:
[1] modified the server resolver code to send ENOENT instead of
ESTALE to older clients for all FOPS. This caused dht_mkdir
to fail under certain conditions (see bug description).

Fix:
Since [1] is needed by AFR only in its lookup path, reverted the changes
introduced by [1]  in resolve_entry_simple () an resolve_inode_simple () and
made the change instead in server_lookup_resume().

[1] http://review.gluster.org/#/c/8080

Change-Id: Idb2de25839fe712550486f2263a60c0531530d8f
BUG: 1118574
Signed-off-by: Ravishankar N 
Reviewed-on: http://review.gluster.org/8294
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra G 
Reviewed-by: Niels de Vos

nfs: prevent assertion error with MOUNT over UDP

2014-07-10T07:15:18+00:00

The MOUNT service over UDP runs in a separate thread. This thread does
not have the correct *THIS xlator set. *THIS points to the global (base)
xlator structure, but GF_CALLOC() requires it to be the NFS-xlator so
that assertions can get validated correctly.

This is solved by passing the NFS-xlator to the pthread function, and
setting the *THIS pointer explicitly in the new thread.

It seems that on occasion (needs further investigation) MOUNT over UDP
does not unregister itself. There can also be issues when the kernel NLM
implementation has been registered at portmap/rpcbind, so adding some
unregister procedures in the cleanup of the test-cases.

Cherry picked from commit ec74ceedaa41047b88d270c00eeb071b73e19664:
> Change-Id: I3be5a420fc800bbcc14198d0b6faf4cf2c7300b1
> BUG: 1116503
> Signed-off-by: Niels de Vos 
> Reviewed-on: http://review.gluster.org/8241
> Reviewed-by: Santosh Pradhan 
> Tested-by: Gluster Build System 
> Reviewed-by: Vijay Bellur 

Change-Id: I3be5a420fc800bbcc14198d0b6faf4cf2c7300b1
BUG: 1116997
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/8258
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Santosh Pradhan

rpcsvc: Validate RPC procedure number before fetch

2014-07-08T10:36:18+00:00

While accessing the procedures of given RPC program in,
rpcsvc_get_program_vector_sizer(), It was not checking boundary
conditions which would cause buffer overflow and subsequently SEGV.

Make sure rpcsvc_actor_t arrays have numactors number of actors.

FIX:
Validate the RPC procedure number before fetching the actor.

Upstream main review: http://review.gluster.org/7726

BUG: 1096020

Change-Id: Iaf207ee976cb56fa9a554ec82c9eab36d3b289ed
Signed-off-by: Santosh Kumar Pradhan 
Reviewed-on: http://review.gluster.org/8228
Tested-by: Gluster Build System 
Reviewed-by: Niels de Vos