r3336: use a struct ntvfs_async_state to be able to do async chaning of ntvfs modules

the idea is that a passthru module can use ntvfs_async_state_push() before
calling ntvfs_next_*() and in the _send function it calls
ntvfs_async_state_pop() and then call the upper layer send_fn itself

- ntvfs_nbench is now fully async

- the ntvfs_map_*() functions and the trans(2) mapping functions are not converted yet

metze
(This used to be commit fde64c0dc142b53d128c8ba09af048dc58d8ef3a)

1 files changed, 3 insertions, 4 deletions

diff --git a/source4/smb_server/smb_server.c b/source4/smb_server/smb_server.c
index ff83bfc80c..86a876554f 100644
--- a/source4/smb_server/smb_server.c
+++ b/source4/smb_server/smb_server.c
@@ -621,10 +621,10 @@ static void construct_reply(struct smbsrv_request *req)
 		return;
 	}
 
-
-	req->smbpid = SVAL(req->in.hdr,HDR_PID);	
 	req->flags = CVAL(req->in.hdr, HDR_FLG);
 	req->flags2 = SVAL(req->in.hdr, HDR_FLG2);
+	req->smbpid = SVAL(req->in.hdr,HDR_PID);
+	req->mid = SVAL(req->in.hdr,HDR_MID);
 
 	if (!req_signing_check_incoming(req)) {
 		req_reply_error(req, NT_STATUS_ACCESS_DENIED);
@@ -694,8 +694,7 @@ void chain_reply(struct smbsrv_request *req)
 
 	/* the current request in the chain might have used an async reply,
 	   but that doesn't mean the next element needs to */
-	ZERO_STRUCT(req->async);
-	req->control_flags &= ~REQ_CONTROL_ASYNC;
+	ZERO_STRUCTP(req->async_states);
 
 	switch_message(chain_cmd, req);
 	return;