diff options
author | Mohammed Rafi KC <rkavunga@redhat.com> | 2019-04-01 14:44:20 +0530 |
---|---|---|
committer | Raghavendra G <rgowdapp@redhat.com> | 2019-04-11 03:47:41 +0000 |
commit | 0496523d3c1ac874eeecbb0ecb6516d88438d3c9 (patch) | |
tree | 0bc1f1577c1204fbbcbeac72855b11507e06e6e8 /THANKS | |
parent | d82640511f51a79db6dabea8599c805028fefafb (diff) |
client/fini: return fini after rpc cleanup
There is a race condition in rpc_transport later
and client fini.
Sequence of events to happen the race condition
1) When we want to destroy a graph, we send a parent down
event first
2) Once parent down received on a client xlator, we will
initiates a rpc disconnect
3) This will in turn generates a child down event.
4) When we process child down, we first do fini for
Every xlator
5) On successful return of fini, we delete the graph
Here after the step 5, there is a chance that the fini
on client might not be finished. Because an rpc_tranpsort
ref can race with the above sequence.
So we have to wait till all rpc's are successfully freed
before returning the fini from client
Change-Id: I20145662d71fb837e448a4d3210d1fcb2855f2d4
fixes: bz#1659708
Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
Diffstat (limited to 'THANKS')
0 files changed, 0 insertions, 0 deletions