From 615482a83d6c18ead7d18624f157170effdebdf8 Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Thu, 7 Oct 2010 22:01:28 +0200 Subject: 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 Autobuild-Date: Fri Oct 8 20:48:11 UTC 2010 on sn-devel-104 --- source3/smbd/oplock.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'source3') diff --git a/source3/smbd/oplock.c b/source3/smbd/oplock.c index cbb8b16a6a..6f4d5780f3 100644 --- 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 } -- cgit