From 693cb77b2fdb96205ab83bb2c22b67fe91de61b0 Mon Sep 17 00:00:00 2001 From: Stefan Metzmacher Date: Wed, 9 Nov 2011 11:47:33 +0100 Subject: s3:smb2_server: always send STATUS_PENDING responses, but delayed by 0.5 milliseconds In future we'll pass the delay from the caller. metze --- source3/smbd/smb2_read.c | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) (limited to 'source3/smbd/smb2_read.c') diff --git a/source3/smbd/smb2_read.c b/source3/smbd/smb2_read.c index 405e82d0f7..75494373c6 100644 --- a/source3/smbd/smb2_read.c +++ b/source3/smbd/smb2_read.c @@ -466,14 +466,8 @@ static struct tevent_req *smbd_smb2_read_send(TALLOC_CTX *mem_ctx, if (NT_STATUS_IS_OK(status)) { /* - * Doing an async read. Don't - * send a "gone async" message - * as we expect this to be less - * than the client timeout period. - * JRA. FIXME for offline files.. - * FIXME. Add cancel code.. + * Doing an async read. */ - smb2req->async = true; return req; } -- cgit