From e3c4f75e6cff378e04fbbc3b01e48cc1ac546194 Mon Sep 17 00:00:00 2001 From: Gordon Ross Date: Fri, 23 Dec 2016 14:30:22 -0500 Subject: 10959 intended nbmand locking functionality is confused Reviewed by: Matt Barden Reviewed by: Evan Layton Reviewed by: Yuri Pankov Approved by: Joshua M. Clulow --- usr/src/lib/smbsrv/libfksmbsrv/common/fksmb_init.c | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'usr/src/lib') diff --git a/usr/src/lib/smbsrv/libfksmbsrv/common/fksmb_init.c b/usr/src/lib/smbsrv/libfksmbsrv/common/fksmb_init.c index f3e7463cb7..80d62d0534 100644 --- a/usr/src/lib/smbsrv/libfksmbsrv/common/fksmb_init.c +++ b/usr/src/lib/smbsrv/libfksmbsrv/common/fksmb_init.c @@ -68,6 +68,17 @@ uint_t smb_audit_flags = 0; #endif +/* + * We don't normally have nbmand support in the test share + * used by fksmbd, but we'd still like the locking code + * to be testable. Intereactions with NFS etc. are not a + * concern in fksmbd, so allow it to use advisory locks. + * + * Should fix the fksmbd test share so it supports nbmand, + * and then set this to zero like the real server. + */ +int smb_allow_advisory_locks = 1; /* See smb_vops.c */ + /* * Maximum number of simultaneous authentication, share mapping, pipe open * requests to be processed. -- cgit v1.2.3