glusterfs.git/xlators/protocol, branch v9dev

protocol/server: Fix coverity issue RESOURCE_LEAK

2020-04-10T03:29:44+00:00

Handle case of arg not freed
CID: 1422174

Updates: #1060
Change-Id: Ibd03908a3ea8369035c2b7f6e024b3e5be48f436
Signed-off-by: Sheetal Pamecha

core[brick_mux]: brick crashed when creating and deleting volumes over time

2020-03-27T15:19:20+00:00

Problem: In brick_mux environment, while volumes are created/stopped in a loop
         after running a long time the main brick is crashed.The brick is crashed
         because the main brick process was not cleaned up memory for all objects
         at the time of detaching a volume.
         Below are the objects that are missed at the time of detaching a volume
         1) xlator object for a brick graph
         2) local_pool for posix_lock xlator
         3) rpc object cleanup at quota xlator
         4) inode leak at brick xlator

Solution: To avoid the crash resolve all leak at the time of detaching a brick
Change-Id: Ibb6e46c5fba22b9441a88cbaf6b3278823235913
updates: #977
Signed-off-by: Mohit Agrawal

protocol/client: fallback to anonymous fd for fsync

2020-03-10T06:53:16+00:00

Change-Id: I32f801206ce7fbd05aa693f44c2f140304f2e275
Fixes: bz#1810842

protocol/client: structure logging

2020-03-03T11:56:44+00:00

convert gf_msg() to gf_smsg()

Updates: #657

Change-Id: I76a09cfd283bb4ec5c4358536da66547aaf0de31
Signed-off-by: yatip

protocol/server-helpers: structure logging

2020-03-03T11:56:10+00:00

convert gf_msg() to gf_smsg()

Updates: #657

Change-Id: Ic7b38b646fa0932f7c1562467866137c4567e1f1
Signed-off-by: yatip

protocol/server-rpc-fops_v2: structure logging

2020-03-03T11:56:10+00:00

convert gf_msg() to gf_smsg()

Updates: #657

Change-Id: I01146bcd06bca44faeca29da48fab1ee3fc51e00
Signed-off-by: yatip

protocol/server: structure logging

2020-03-03T11:56:10+00:00

Convert all gf_msg() to gf_smsg()

Updates: #657
Change-Id: Ic54b03f05e2766c87f50df0b3a66803b5519fad9
Signed-off-by: yatip

dht: Fix stale-layout and create issue

2020-02-09T02:51:31+00:00

Problem: With lookup-optimize set to on by default, a client with
stale-layout can create a new file on a wrong subvol. This will lead to
possible duplicate files if two different clients attempt to create the
same file with two different layouts.

Solution: Send in-memory layout to be cross checked at posix before
commiting a "create". In case of a mismatch, sync the client layout with
that of the server and attempt the create fop one more time.

test: Manual, testcase(attached)

fixes: bz#1786679
Change-Id: Ife0941f105113f1c572f4363cbcee65e0dd9bd6a
Signed-off-by: Susant Palai

protocol/client-rpc-fops: structure logging

2020-02-06T05:26:44+00:00

convert all gf_msg() to gf_smsg()

Updates: #657

Change-Id: Ia9d4fb17579af6586bc13d69ec7990c6cf220aac
Signed-off-by: yatip

protocol/client: Maintain connection to brick status

2020-02-05T12:13:05+00:00

Problem:
The current version of the code depends on the non-zero-port information to
propagate ping event from brick to parent layers. But as and when connection
succeeds, port is set to zero in rpc layer.So ping event is never propagated to
parent layers. Halo doesn't work without this.

Fix:
Remember the status of connection in 'private' structure and use that to decide
to propagate ping event to parent xlator.

fixes: bz#1797934
Change-Id: Ia578ba9fb3813953d2068dbba5c982ab27cc3429
Signed-off-by: Pranith Kumar K