glusterfs.git, branch v4.0dev

run-tests.sh: log failed tests at the end

2017-07-21T12:38:40+00:00

Two benefits:

1. People who subscribe to emails on regression failures
   (like maintainers@gluster.org), can see the list of failed tests
   in the email itself, instead of clicking on the link and checking
   for failures.

2. When we visit the regression console, instead of scrolling to the
   exact position to see which tests failed, we can just press 'End'
   and would be able to check failures.

Change-Id: Ibb4ac9575c5d32bae9c40c31fb53c9488b94421a
Signed-off-by: Amar Tumballi 
Reviewed-on: https://review.gluster.org/17843
Smoke: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Niels de Vos 
Reviewed-by: Jeff Darcy 
CentOS-regression: Gluster Build System

geo-rep: Handle possible entry failures gracefully

2017-07-21T10:38:12+00:00

Updates: #246

Change-Id: If0ce83fe8dd3068bfb671f398b2e82ac831288d0
Signed-off-by: Kotresh HR 
Reviewed-on: https://review.gluster.org/17577
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Aravinda VK

nfs: improve error handling for WebNFS mount permissions

2017-07-21T10:17:36+00:00

In case nfs3_funge_webnfs_zerolen_fh() returns an error, the
nfs3_call_state_t structure will not get initialized. This means that
calling `nfs3_call_state_wipe (cs)` will result in a segmentation fault
after commit daed52b8eb that makes nfs3_call_state_t refcounted.

Change-Id: I4c300aedf132a7fea95756dd278ff87d67722478
BUG: 1468291
Fixes: e3f48fa2 ("nfs: add permission checking for mounting over WebNFS")
Signed-off-by: Niels de Vos 
Reviewed-on: https://review.gluster.org/17822
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: jiffin tony Thottan 
Reviewed-by: soumya k

tools/glusterfind: Fix encoding to encode only space,newline and percent chars

2017-07-21T08:41:13+00:00

libgfchangelog was encoding path using spec rfc3986, but encoding only
required for SPACE, NEWLINE and PERCENT chars since the NEWLINE char is
used as record separator and SPACE as field separator in the parsed
changelogs output.

Changed the encoding function to encode only SPACE, NEWLINE and PERCENT chars

BUG: 1451724
Change-Id: Ic1dea824d23493dedcf3db45f353f90572f4e046
Signed-off-by: Aravinda VK 
Reviewed-on: https://review.gluster.org/17788
CentOS-regression: Gluster Build System 
Smoke: Gluster Build System 
Reviewed-by: Milind Changire

rpc: include current second in timed out frame cleanup

2017-07-21T06:22:21+00:00

Problem:
frames which time out at current second are missed out

Solution:
change test to include frames timing out at current second
i.e. timeout <= current.tv_sec
instead of
timeout < current.tv_sec

Change-Id: I459d47856ade2b657a0289e49f7f63da29186d6e
BUG: 1468433
Signed-off-by: Milind Changire 
Reviewed-on: https://review.gluster.org/17722
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Raghavendra G

geo-rep: Fix changelog encoding to encode only space and newline

2017-07-21T04:44:30+00:00

libgfchangelog was encoding path using spec rfc3986, but encoding only
required for SPACE and NEWLINE chars since the NEWLINE char is used as
record separator and SPACE as field separator in the parsed changelogs
output.

Changed the encoding function to encode only SPACE and NEWLINE.

BUG: 1451724
Change-Id: I1936efad31788a9e636f912c832ed7d7efea4fe2
Signed-off-by: Aravinda VK 
Reviewed-on: https://review.gluster.org/17787
Reviewed-by: Prashanth Pai 
Reviewed-by: Kotresh HR 
CentOS-regression: Gluster Build System 
Smoke: Gluster Build System

features/libgfchangelog: Fix encoding to encode only space and newline

2017-07-21T04:43:58+00:00

libgfchangelog was encoding path using spec rfc3986, but encoding only
required for SPACE and NEWLINE chars since the NEWLINE char is used as
record separator and SPACE as field separator in the parsed changelogs
output.

Changed the encoding function to encode only SPACE and NEWLINE.

BUG: 1451724
Change-Id: I4305459aab9e710517dd3eb065f0024503064b77
Signed-off-by: Aravinda VK 
Reviewed-on: https://review.gluster.org/17674
Smoke: Gluster Build System 
Reviewed-by: Prashanth Pai 
CentOS-regression: Gluster Build System 
Reviewed-by: Kotresh HR

MAINTAINERS: Changes for Maintainers 2.0

2017-07-20T22:49:42+00:00

Updates MAINTAINERS to be in sync with [1]. More details on Maintainers
2.0 can be found at [2].

[1] https://goo.gl/CcvP5K
[2] https://hackmd.io/s/SkwiZd4qe

Change-Id: I069ee8eb78ec4f5272052f3ba902eb29f0fdb64b
BUG: 1463365
Signed-off-by: Vijay Bellur 
Reviewed-on: https://review.gluster.org/17583
Reviewed-by: Niels de Vos 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Tested-by: Amar Tumballi 
Reviewed-by: Amar Tumballi 
Reviewed-by: jiffin tony Thottan 
Reviewed-by: soumya k 
Reviewed-by: mohammed rafi  kc

glusterd: fix brick start race

2017-07-20T21:50:19+00:00

Problem:

Another race where glusterd was restarted glusterd_brick_start () is called
multiple times due to friend handshaking and in one instance when one of the
brick was attempted to be attached to the existing brick process,
send_attach_req failed as the first brick itself was still not up and then we
did a synlock_unlock () followed by a sleep of 1 sec, before the same thread
woke up, another thread tried to start the same brick process and then it
assumed that it has to start a fresh brick process.

Solution:

1. If brick is in starting phase (brickinfo->status ==
GF_BRICK_STARTING), no need for a reattempt to
start the brick.
2. While initiating attach_req set brickinfo->status to
GF_BRICK_STARTING

Change-Id: Ib007b6199ec36fdab4214a1d37f99d7f65ef64da
BUG: 1465559
Signed-off-by: Atin Mukherjee 
Reviewed-on: https://review.gluster.org/17840
Reviewed-by: Amar Tumballi 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Jeff Darcy

cluster/dht: Fixed crash in dht_rmdir_is_subvol_empty

2017-07-20T12:45:59+00:00

The local->call_cnt was being accessed and updated inside
the loop where the entries were being processed and the calls
were being wound.
This could end up in a scenario where the local->call_cnt became
0 before the processing was complete causing the crash when the
next entry was being processed.

Change-Id: I930f61f1a1d1948f90d4e58e80b7d6680cf27f2f
BUG: 1472949
Signed-off-by: N Balachandran 
Reviewed-on: https://review.gluster.org/17825
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-by: Amar Tumballi 
Reviewed-by: Shyamsundar Ranganathan