r3039: This solves the problem of async handlers in ntvfs backends not being

in the right state when called. For example, when we use the unixuid
handler in the chain of handlers, and a backend decides to continue a
call asynchronously then we need to ensure that the continuation
happens with the right security context.

The solution is to add a new ntvfs operation ntvfs_async_setup(),
which calls all the way down through the layers, setting up anything
that is required, and takes a private pointer. The backend wanting to
make a async calls can use ntvfs_async_setup() to ensure that the
modules above it are called when doing async processing.
(This used to be commit a256e71029727fa1659ade6257085df537308c7d)

1 files changed, 11 insertions, 0 deletions

diff --git a/source4/ntvfs/simple/vfs_simple.c b/source4/ntvfs/simple/vfs_simple.c
index 7f5d447a09..7ebc040608 100644
--- a/source4/ntvfs/simple/vfs_simple.c
+++ b/source4/ntvfs/simple/vfs_simple.c
@@ -623,6 +623,16 @@ static NTSTATUS svfs_logoff(struct ntvfs_module_context *ntvfs,
 }
 
 /*
+  setup for an async call
+*/
+static NTSTATUS svfs_async_setup(struct ntvfs_module_context *ntvfs,
+				 struct smbsrv_request *req, 
+				 void *private)
+{
+	return NT_STATUS_OK;
+}
+
+/*
   lock a byte range
 */
 static NTSTATUS svfs_lock(struct ntvfs_module_context *ntvfs,
@@ -999,6 +1009,7 @@ NTSTATUS ntvfs_simple_init(void)
 	ops.search_close = svfs_search_close;
 	ops.trans = svfs_trans;
 	ops.logoff = svfs_logoff;
+	ops.async_setup = svfs_async_setup;
 
 	/* register ourselves with the NTVFS subsystem. We register
 	   under names 'simple'