[cifs-protocol] [REG:113011010129494] FSCTL_SRV_COPYCHUNK overlapping ranges
edgaro at microsoft.com
Thu Jan 10 11:38:40 MST 2013
[Updating subject with new case number 113011010129494]
Thanks for the feedback.
This case will be addressing the remaining comments regarding the update to [MS-SMB2] 126.96.36.199.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.
From: David Disseldorp [mailto:ddiss at suse.de]
Sent: Thursday, January 10, 2013 8:34 AM
To: David Disseldorp
Cc: Edgar Olougouna; cifs-protocol at cifs.org; pfif at 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 <ddiss at 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.
More information about the cifs-protocol