protocol/client: don't reopen fds on which POSIX locks are held after a reconnect

Bricks cleanup any granted locks after a client disconnects and
currently these locks are not healed after a reconnect. This means
post reconnect a competing process could be granted a lock even though
the first process which was granted locks has not unlocked. By not
re-opening fds, subsequent operations on such fds will fail forcing
the application to close the current fd and reopen a new one. This way
we prevent any silent corruption.

A new option "client.strict-locks" is introduced to control this
behaviour. This option is set to "off" by default.

Change-Id: Ieed545efea466cb5e8f5a36199aa26380c301b9e
Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
updates: bz#1694920

0 files changed, 0 insertions, 0 deletions