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

..

cmirrord

cov: mask some warning about leakage

2021-09-20 14:26:09 +02:00

dmeventd

gcc: match types

2021-09-22 17:18:50 +02:00

lvmdbusd

lvmdbusd: Use ID_FS_TYPE UDev property in udevwatch

2021-10-07 12:42:44 -05:00

lvmlockd

lvmlockd: cleanup after sanlock_rem_lockspace error

2022-01-04 14:53:47 -06:00

lvmpolld

cov: add some initializers

2021-09-13 12:34:41 +02:00

Makefile.in

build: Remove lvmetad leftovers

2018-07-24 15:02:32 +02:00