s3:vfs_fileid: introduce 'fileid:nolock_max_slots'

This controlls the maximum number of concurrent locking slots
on each host. It specifies the maximal number of locking.tdb
records for a single inode.

It can be used to deliberately break lock coherency not
only between cluster nodes, but also between processes on
each node.

This allows administrators to control the behavior that's
currently only available by 'fsname_norootdir_ext' to
other cases as well.

Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Ralph Boehme <slow@samba.org>

diff --git a/source3/modules/vfs_fileid.c b/source3/modules/vfs_fileid.c
index 9ef0d6919df90cda1f1397772ca9df71f07b7f8f..f9472c275ee2a587c448b3ec8d248140f2899a8d 100644 (file)
--- a/source3/modules/vfs_fileid.c
+++ b/source3/modules/vfs_fileid.c
@@ -575,6 +575,9 @@ static int fileid_connect(struct vfs_handle_struct *handle,
                }
        }
 
+       max_slots = lp_parm_ulonglong(SNUM(handle->conn),
+                                     "fileid", "nolock_max_slots",
+                                     max_slots);
        max_slots = MAX(max_slots, 1);
 
        data->nolock.extid = fileid_mapping_nolock_extid(max_slots);