glusterfs.git, branch v5.4

doc: Added release notes for release 5.4

2019-02-26T14:21:12+00:00

Change-Id: I6aaa93edc4ae7d018c83c5d23d536075c013d0b5
fixes: bz#1667103
Signed-off-by: ShyamsundarR

eventsapi: Fix Python3 compatibility issues

2019-02-26T05:11:49+00:00

- Fixed Relative import and non-package import related issues.
- socketserver import issues fix
- Renamed installed directory name to `gfevents` from `events`(To
  avoid any issues with other global libs)

Fixes: bz#1649054
Change-Id: I3dc38bc92b23387a6dfbcc0ab8283178235bf756
Signed-off-by: Aravinda VK 
(cherry picked from commit cd68f7b88b9a2c9a4e4ff9fca61517384e54130a)

packaging: Obsoleting glusterfs-gnfs for upgrade

2019-02-25T15:23:26+00:00

Master refs
>    https://review.gluster.org/#/c/glusterfs/+/22253/
>    fixes: bz#1672711
>    Change-Id: Iad7194e788a8eeecd617614e9f8a1fe3264a384d
>    Signed-off-by: Sahina Bose 
>    Signed-off-by: Jiffin Tony Thottan 

Fixes: bz#1679968
Change-Id: Ib66d15953abb2645238f01c8ee9df54d2b35736a
Signed-off-by: Kaleb S. KEITHLEY 
Signed-off-by: Jiffin Tony Thottan

socket: socket event handlers now return void

2019-02-25T15:23:11+00:00

Problem:
Returning any value from socket event handlers to the event sub-system
doesn't make sense since event sub-system cannot handle socket
sub-system errors.

Solution:
Change return type of all socket event handlers to 'void'

mainline:
> Reviewed-on: https://review.gluster.org/c/glusterfs/+/22221

Change-Id: I70dc2c57f12b7ea2fae41120f71aa0d7fe0b2b6f
Fixes: bz#1651246
Signed-off-by: Milind Changire 
(cherry picked from commit 776ba851c6ee6c265253d44cf1d6e4e3d4a21772)

fuse: reflect the actual default for lru-limit option

2019-02-25T15:16:31+00:00

in both `--help` text and man page

updates: bz#1667103
Change-Id: I9aa9367c6863ac8e2403255280697c9e6be26cf0
Signed-off-by: Amar Tumballi

performance/write-behind: fix use-after-free in readdirp

2019-02-22T14:50:00+00:00

Two issues were found:
1. in wb_readdirp_cbk, inode should unrefed after wb_inode is
unlocked. Otherwise, inode and hence the context wb_inode can be freed
by the type we try to unlock wb_inode
2. wb_readdirp_mark_end iterates over a list of wb_inodes of children
of a directory. But inodes could've been freed and hence the list
might be corrupted. To fix take a reference on inode before adding it
to invalidate_list of parent.

Change-Id: I911b0e0b2060f7f41ded0b05db11af6f9b7c09c5
Signed-off-by: Raghavendra Gowdappa 
Updates: bz#1671556

performance/write-behind: handle call-stub leaks

2019-02-22T14:49:13+00:00

Change-Id: I7be9a5f48dcad1b136c479c58b1dca1e0488166d
Signed-off-by: Raghavendra Gowdappa 
Fixes: bz#1671556
(cherry picked from commit 6175cb10cd5f59f3c7ae4100bc78f359b68ca3e9)

md-cache: Adapt integer data types to avoid integer overflow

2019-02-20T14:00:05+00:00

The "struct iatt" in iatt.h is using int64_t types for storing
the atime, mtime and ctime. Therefore the struct 'struct md_cache' in
md-cache.c should also use this types to avoid an integer overflow.

This can happen e.g. if someone uses a very high default-retention-period
in the WORM-Xlator.

Change-Id: I605268d300ab622b9c8ab30e459dc00d9340aad1
fixes: bz#1678726
Signed-off-by: David Spisla 
(cherry picked from commit 15423e14f16dd1a15ee5e5cbbdbdd370e57ed59f)

cluster/thin-arbiter: Consider thin-arbiter before marking new entry changelog

2019-02-18T14:39:55+00:00

If a fop to create an entry fails on one of the data brick,
we mark the pending changelog on the entry on brick for which
it was successful. This is done as part of post op phase to
make sure that entry gets healed even if it gets renamed to
some other path where its parent was not marked as bad.

As it happens as part of post op, we should consider thin-arbiter
to check if the brick, which was successful, is the good brick or not.
This will avoide split brain and other issues.

>Change-Id: I12686675be98f02f70a5186b3ed748c541514d53
>Signed-off-by: Ashish Pandey 

Change-Id: I12686675be98f02f70a5186b3ed748c541514d53
updates: bz#1672314
Signed-off-by: Ashish Pandey

Bump up timeout for tests on AWS

2019-02-07T08:02:01+00:00

Fixes: bz#1673268
Change-Id: I2b9be45f199f6436b858536c6f49be85902217f0
Signed-off-by: Nigel Babu