diff options
| author | Alexander Aring <aahringo@redhat.com> | 2022-06-22 14:45:15 -0400 |
|---|---|---|
| committer | David Teigland <teigland@redhat.com> | 2022-06-24 11:57:47 -0500 |
| commit | 682bb91b6ba829e4efc635630610444141ee567d (patch) | |
| tree | 76288f5934ba0b7a5f07a2b1664497efb76ed484 /fs/ext2 | |
| parent | 7e09b15cfe7b6a6135448015482112869722a763 (diff) | |
| download | linux-stable-682bb91b6ba829e4efc635630610444141ee567d.tar.gz linux-stable-682bb91b6ba829e4efc635630610444141ee567d.tar.bz2 linux-stable-682bb91b6ba829e4efc635630610444141ee567d.zip | |
fs: dlm: make new_lockspace() wait until recovery completes
Make dlm_new_lockspace() wait until a full recovery completes
sucessfully or fails. Previously, dlm_new_lockspace() returned
to the caller after dlm_recover_members() finished, which is
only partially through recovery. The result of the previous
behavior is that the new lockspace would not be usable for some
time (especially with overlapping recoveries), and some errors
in the later part of recovery could not be returned to the caller.
Kernel callers gfs2 and cluster-md have their own wait handling to
wait for recovery to complete after calling dlm_new_lockspace().
This continues to work, but will be unnecessary.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
Diffstat (limited to 'fs/ext2')
0 files changed, 0 insertions, 0 deletions