David Teigland 0c1d3db8db lvmlockd: accept repeated global lock requests ...

It's not an error if a command requests the global lock
when it has already acquired it.  It shouldn't happen,
but there could be cases we've not found.

2018-05-30 09:25:45 -05:00

..

.exported_symbols

Pre-release cleanups.

2009-05-21 03:04:52 +00:00

cluster_locking.c

debug: add stack tracking

2018-02-12 22:15:03 +01:00

external_locking.c

doc: change fsf address

2016-01-21 12:11:37 +01:00

file_locking.c

coverity: drop unneeded header files

2018-03-17 23:33:58 +01:00

locking_types.h

doc: change fsf address

2016-01-21 12:11:37 +01:00

locking.c

Remove lvm1 and pool disk formats

2018-04-30 16:55:02 -05:00

locking.h

pvmove: reinstantiate clustered pvmove

2018-02-01 21:55:20 +01:00

lvmlockd.c

lvmlockd: accept repeated global lock requests

2018-05-30 09:25:45 -05:00

lvmlockd.h

lvmlockd: print error about starting lock manager

2017-08-28 16:24:00 -05:00

Makefile.in

doc: change fsf address

2016-01-21 12:11:37 +01:00

no_locking.c

doc: change fsf address

2016-01-21 12:11:37 +01:00