glusterfs.git, branch release-7

doc: Added release 7.9 notes (#1865)

2020-12-01T05:31:17+00:00

Updates: #1864

Change-Id: I01fe520817fd44670b4dfc917bfa2ba39ecffe9b
Signed-off-by: Rinku Kothiya

glusterd: Can't run rebalance due to long unix socket (#1853)

2020-11-27T07:25:32+00:00

Problem: glusterd populate unix socket file name based
         on volname and if volname is lengthy socket
         system call's are failed due to breach maximum length
         is defined in the kernel.

Solution:Convert unix socket name to hash to resolve the issue

> Change-Id: I5072e8184013095587537dbfa4767286307fff65
> fixes: bz#1720566
> Signed-off-by: Mohit Agrawal 
> (Cherry pick from commit 2d7b77eb971700c1073db2b74f5877c1ae8293fc)
> (Reviewed on upstream link https://review.gluster.org/#/c/glusterfs/+/22869/)

Fixes: #1852
Change-Id: I4c3b22344ecfcd1fc9e8292cdc8a11f895d9f78c
Signed-off-by: Mohit Agrawal

posix: In the commit 2f044c4587c6db3cb82b6128f056ec2ea2bc1b98 the ret (#1837) (#1845)

2020-11-27T07:12:53+00:00

update was missed in the function posix_get_gfid2path if
       GF_MALLOC is failed.

Solution: Update the ret value to -1 if GF_MALLOC is failed

Fixes: #1836
Change-Id: I510ebf0605ee49b84ff3570948771319f283b10e
Signed-off-by: Mohit Agrawal

glusterd: resource leaks (#1839)

2020-11-27T07:06:39+00:00

* glusterd: resource leaks

Issue:
iobref was not freed before exiting the function
if all the checks were OK, which caused the resource
leak.

Fix:
Modified the code a bit to avoid use of an extra reference
to the label, and to free the iobref and iobuf if not NULL,
and then exit the function.

CID: 1430118

Updates: #1060

Signed-off-by: nik-redhat 

* Updated the changes

Change-Id: If07298cdc0add4bdd771ce9b0bbce08cafc0c7c6
Signed-off-by: nik-redhat

CLI: Added an error message in case of timeout (#1841)

2020-11-25T06:12:18+00:00

Added an error message in CLI when there are volumes present in the cluster
but timeout happens while fetching them.

This PR fixes #1738

Signed-off-by: nik-redhat

posix: Use MALLOC instead of alloca to allocate memory for xattrs list (#1730) (#1828)

2020-11-24T06:27:28+00:00

In case of file is having huge xattrs on backend a brick process is
crashed while alloca(size) limit has been crossed 256k because iot_worker
stack size is 256k.

Fixes: #1699
Signed-off-by: Mohit Agrawal 

Change-Id: I100468234f83329a7d65b43cbe4e10450c1ccecd

fixed AFR_READ_POLICY_GFID_PID_HASH policy bug (#1562)

2020-10-27T12:43:52+00:00

Change-Id: Ib927a770a486c95e4b157e76ba96e9904d1a9716
Fixes: #1499
Signed-off-by: perrynzhou 

Co-authored-by: perrynzhou

rfc.sh: Move -> github flow (#1606)

2020-10-13T10:16:56+00:00

Change-Id: I73b7dc0e461aa09a38be0c444255bb168315bc41
Fixes: #1604
Signed-off-by: Pranith Kumar K

features/bit-rot: invalid snprintf() buffer size

2020-09-29T12:52:44+00:00

Found with clang-10 -Wfortify-source:

bit-rot-scrub.c:1802:15: warning: 'snprintf' size argument is too large;
destination buffer has size 32, but size argument is 4096 [-Wfortify-source]
        len = snprintf(key, PATH_MAX, "quarantine-%d", j);
              ^
bit-rot-scrub.c:1813:9: warning: 'snprintf' size argument is too large;
destination buffer has size 32, but size argument is 4096 [-Wfortify-source]
        snprintf(main_key, PATH_MAX, "quarantine-%d", tmp_count);

Change-Id: I9b9c09ef2223ed181d81215154345de976b82f13
Signed-off-by: Dmitry Antipov 
Fixes: #1221

doc: Added release 7.8 notes

2020-09-28T06:21:31+00:00

Fixes: #1517

Change-Id: I9bbd28ef3614fdcbce11e798a38149a5e00b75c0
Signed-off-by: Rinku Kothiya