Anoop C S 80c9219d60 s3/locking: Fix assertion check on lock reference count ...

lock_ref_count will always hold the old value prior to change. Thus it
would mean that if lock_ref_count is 0 the new value is already -1 which
is not expected here. Therefore it is better to make sure that it is
always greater than 0 rather than >= 0.

Signed-off-by: Anoop C S <anoopcs@redhat.com>
Reviewed-by: Jeremy Allison <jra@samba.org>
Reviewed-by: Andreas Schneider <asn@samba.org>

Autobuild-User(master): Jeremy Allison <jra@samba.org>
Autobuild-Date(master): Tue Jul 31 04:23:47 CEST 2018 on sn-devel-144

2018-07-31 04:23:47 +02:00

..

brlock.c

lib: Add lib/util/server_id.h

2017-01-22 18:30:11 +01:00

leases_db.c

leases_db: don't leak lock_path onto talloc tos

2015-01-12 19:22:30 +01:00

leases_db.h

s3:locking: Change the data model for leases_db to cope with dynamic path renames.

2014-12-09 03:44:04 +01:00

leases_util.c

s3/locking: helper functions for lease types

2017-05-06 19:01:14 +02:00

locking.c

smbd: Remove "share_mode_entry->lease"

2018-07-27 01:42:31 +02:00

posix.c

s3/locking: Fix assertion check on lock reference count

2018-07-31 04:23:47 +02:00

proto.h

smbd: Pass "share_mode_data" to share_entry_forall callback

2018-07-26 22:44:25 +02:00

share_mode_lock.c

smbd: Remove "share_mode_entry->lease"

2018-07-27 01:42:31 +02:00