[Updating subject with new case number 113011010129494] David,
Thanks for the feedback. This case will be addressing the remaining comments regarding the update to [MS-SMB2] 3.3.5.15.6 Handling a Server-Side Data Copy Request: The remaining two comments: I think the entry stating the destination file FILE_READ_DATA access requirement for FSCTL_SRV_COPYCHUNK should remain here, as Windows servers appear to implement this (tested against 2012 and 2008r2). ... This may imply that the entire chunk must be read and then subsequently written, contrary to Windows Server 2008r2's sub chunk-length (2048 byte) copy behaviour described in the initial report. Perhaps an extra Product Behaviour caveat should be added to clarify this. Regards, Edgar -----Original Message----- From: David Disseldorp [mailto:dd...@suse.de] Sent: Thursday, January 10, 2013 8:34 AM To: David Disseldorp Cc: Edgar Olougouna; cifs-protocol@cifs.org; p...@tridgell.net; MSSolve Case Email Subject: Re: [REG:112120310051084] FSCTL_SRV_COPYCHUNK overlapping ranges On Wed, 2 Jan 2013 17:08:47 +0100 David Disseldorp <dd...@suse.de> wrote: > Furthermore, FILE_READ_DATA access on the source file does not appear > to be required. I'd planned to raise this as a separate DocHelp issue. Sorry, disregard this incorrect comment. I was testing with execute access inherently granting read access. Regards, David _______________________________________________ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
