[cifs-protocol] [EXTERNAL] Re: MS-FSA 2.1.4.17 Algorithm for Noting That a File Has Been Modified - TrackingID#2503100040000894

Ralph Boehme slow at samba.org
Mon Mar 17 18:57:07 UTC 2025


Hi Obaid

this wasn't an inquiry for the exact wording, but for the logical change 
in my own wording. Makes sense?

On 3/17/25 7:44 PM, Obaid Farooqi wrote:
> Hi Ralph:
> The final document change is the prerogative of the product team. I only describe the issue with the document and suggest what IMO is the proper update, but I cannot guarantee that.
> 
> 
> Regards,
> Obaid Farooqi
> Escalation Engineer | Microsoft
> 
> -----Original Message-----
> From: Ralph Boehme <slow at samba.org>
> Sent: Monday, March 17, 2025 12:48 PM
> To: Obaid Farooqi <obaidf at microsoft.com>
> Cc: Microsoft Support <supportmail at microsoft.com>; cifs-protocol at lists.samba.org
> Subject: Re: [EXTERNAL] Re: MS-FSA 2.1.4.17 Algorithm for Noting That a File Has Been Modified - TrackingID#2503100040000894
> 
> Hi Obaid,
> 
> On 3/17/25 6:36 PM, Obaid Farooqi wrote:
>> I have filed a bug to update MS-FSA.
>> Please let me know if this does not answer your question.
> iow you'll remove the two sentences
> 
>     If Open.Stream.AllocationSize is equal to NewAllocationSize, the
>     operation MUST return STATUS_SUCCESS.
> 
> and
> 
>     If Open.Stream.Size is equal to InputBuffer.EndOfFile, the
>     operation MUST return STATUS_SUCCESS at this point.
> 
> right?
> 
> Plus mentioning that when extending FileAllocationInformation update changetime, not modificationtime and when shrinking, update both.
> 
> Right?
> 
> Thanks!
> -slow




More information about the cifs-protocol mailing list