From 9f51d610d2d14f2b0ac532019e42bd18b8a05d81 Mon Sep 17 00:00:00 2001 From: Stefan Metzmacher Date: Wed, 8 Aug 2012 12:50:22 +0200 Subject: s3:smb2_server: don't try to update req->in.vector[0] in smbd_smb2_request_pending_queue() req->in.vector[0] is reserved for the transport and might be removed in future. This is currently always { NULL, 0 }, as it's not used, by our transport layer code. The SMB2 layer should never touch this! metze --- source3/smbd/smb2_server.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/source3/smbd/smb2_server.c b/source3/smbd/smb2_server.c index 19a1051f33..4ced9f21fe 100644 --- a/source3/smbd/smb2_server.c +++ b/source3/smbd/smb2_server.c @@ -1232,9 +1232,6 @@ NTSTATUS smbd_smb2_request_pending_queue(struct smbd_smb2_request *req, sizeof(req->in.vector[0])*SMBD_SMB2_NUM_IOV_PER_REQ); req->in.vector_count = req->current_idx + SMBD_SMB2_NUM_IOV_PER_REQ; - /* Reset the new in size. */ - smb2_setup_nbt_length(req->in.vector, req->in.vector_count); - /* Re-arrange the out.vectors. */ memmove(&req->out.vector[req->current_idx], &req->out.vector[i], -- cgit