s3: Hang the isilon kernel oplocks off the NULL context

All I see is a fd_event that does not need a special destructor.

Tim, Steven, I've added the #error as well for you to remove after review.

Thanks,

Volker

Autobuild-User: Volker Lendecke <vlendec@samba.org>
Autobuild-Date: Fri Oct  8 20:48:11 UTC 2010 on sn-devel-104

diff --git a/source3/smbd/oplock.c b/source3/smbd/oplock.c
index cbb8b16a6a750e2ccf3a1878a3a7597d7e54a159..6f4d5780f3b78c85525dbadd0331cd051aa2b4b0 100644 (file)
--- a/source3/smbd/oplock.c
+++ b/source3/smbd/oplock.c
@@ -926,7 +926,8 @@ bool init_oplocks(struct messaging_context *msg_ctx)
 #elif HAVE_KERNEL_OPLOCKS_LINUX
                koplocks = linux_init_kernel_oplocks(NULL);
 #elif HAVE_ONEFS
-               koplocks = onefs_init_kernel_oplocks(talloc_autofree_context());
+#error Isilon, please check if the NULL context is okay here. Thanks!
+               koplocks = onefs_init_kernel_oplocks(NULL);
 #endif
        }