David Teigland 42a16aa6f3 lvmlockd: cleanup after sanlock_rem_lockspace error ... When storage is lost under a sanlock VG, and kill_vg/drop_vg are used, sanlock_rem_lockspace() may return an error, but the cleanup steps should still be performed. Without the cleanup, gl_lsname_sanlock was not cleared. This caused future lock requests to fail with ENOLS, but the NO_GL_LS flag was not set due to gl_lsname_sanlock being set. This caused lockd_global(sh) in lvm commands to fail when they could succeed. Fix from guozhonghua216		2022-01-04 14:53:47 -06:00
..
.gitignore	gitignore: Update for in-place build.	2015-07-27 13:18:35 +01:00
lvmlockctl.c	cov: ensuring buffer is zeroed	2021-09-21 21:03:47 +02:00
lvmlockd-client.h	cleanup: matching declaration order	2020-09-01 17:57:50 +02:00
lvmlockd-core.c	cov: do not drop already known error state	2021-10-15 23:40:56 +02:00
lvmlockd-dlm.c	cov: check strchr for NULL	2021-09-21 21:03:47 +02:00
lvmlockd-idm.c	cleanup: free already does NULL check	2021-09-15 15:24:56 +02:00
lvmlockd-internal.h	lvmlockd: idm: Hook Seagate IDM wrapper APIs	2021-05-20 16:01:04 -05:00
lvmlockd-sanlock.c	lvmlockd: cleanup after sanlock_rem_lockspace error	2022-01-04 14:53:47 -06:00
Makefile.in	lvmlockd: idm: Introduce new locking scheme	2021-05-20 16:00:59 -05:00