[Bugs] [Bug 1584633] Brick process crashed after upgrade from RHGS-3.3.1 async( 7.4) to RHGS-3.4(7.5)

bugzilla at redhat.com bugzilla at redhat.com
Thu May 31 20:30:10 UTC 2018


https://bugzilla.redhat.com/show_bug.cgi?id=1584633

Worker Ant <bugzilla-bot at gluster.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|POST                        |MODIFIED



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/20109 committed in release-4.1 by
"Shyamsundar Ranganathan" <srangana at redhat.com> with a commit message-
protocol/client: Don't send fops till SETVOLUME is complete

An earlier commit set conf->connected just after rpc layer sends
RPC_CLNT_CONNECT event. However, success of socket level connection
connection doesn't indicate brick stack is ready to receive fops, as
an handshake has to be done b/w client and server after
RPC_CLNT_CONNECT event. Any fop sent to brick in the window between,
* protocol/client receiving RPC_CLNT_CONNECT event
* protocol/client receiving a successful setvolume response

can end up accessing an uninitialized brick stack. So, set
conf->connected only after a successful SETVOLUME.

Change-Id: I139a03d2da6b0d95a0d68391fcf54b00e749decf
fixes: bz#1584633
Signed-off-by: Raghavendra G <rgowdapp at redhat.com>
(cherry picked from commit 430e4872db43447c8a15b638760d23c188257139)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list