diff options
| author | Xavi Hernandez <xhernandez@redhat.com> | 2020-03-01 19:49:04 +0100 |
|---|---|---|
| committer | Rinku Kothiya <rkothiya@redhat.com> | 2020-03-16 08:18:51 +0000 |
| commit | 87f1163e83339b2c2923106e0d9a45e8a327bb7a (patch) | |
| tree | 7c99e035c7e49ff20dab46fe8c231ad3fc3057e9 /tests/volume.rc | |
| parent | f3b85b01e4b61a52598a6789c61997c5dad65bf0 (diff) | |
cluster/afr: fix race when bricks come up
The was a problem when self-heal was sending lookups at the same time
that one of the bricks was coming up. In this case there was a chance
that the number of 'up' bricks changes in the middle of sending the
requests to subvolumes which caused a discrepancy in the expected
number of replies and the actual number of sent requests.
This discrepancy caused that AFR continued executing requests before
all requests were complete. Eventually, the frame of the pending
request was destroyed when the operation terminated, causing a use-
after-free issue when the answer was finally received.
In theory the same thing could happen in the reverse way, i.e. AFR
tries to wait for more replies than sent requests, causing a hang.
Backport of:
> Change-Id: I7ed6108554ca379d532efb1a29b2de8085410b70
> Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
> Fixes: bz#1808875
Change-Id: I7ed6108554ca379d532efb1a29b2de8085410b70
Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
Fixes: bz#1809438
Diffstat (limited to 'tests/volume.rc')
0 files changed, 0 insertions, 0 deletions