[cifs-protocol] [EXTERNAL] Flags field in [MS-SMB2] 2.2.14 SMB2 CREATE Response? - TrackingID#2302140040008793

Michael Bowen Mike.Bowen at microsoft.com
Tue Feb 14 21:14:13 UTC 2023

[DocHelp to BCC]

Hi Volker,

Thanks for your question. One of the Open Specifications team members will respond to assist you. In the meantime, we've created case 2302140040008793 to track this request. Please leave the case number in the subject and use reply all when communicating with our team about this request.

Best regards,
Mike Bowen
Escalation Engineer - Microsoft Open Specifications

-----Original Message-----
From: Volker Lendecke <Volker.Lendecke at sernet.de> 
Sent: Tuesday, February 14, 2023 12:24 PM
To: Interoperability Documentation Help <dochelp at microsoft.com>
Cc: cifs-protocol at lists.samba.org
Subject: [EXTERNAL] Flags field in [MS-SMB2] 2.2.14 SMB2 CREATE Response?

Hello dochelp,

[ms-smb2] 2.2.14 defines the flags field in the create response as SMB2_CREATE_FLAG_REPARSEPOINT (0x01) when the last component of a file opened is a reparse point. Receiving an SMB2 CREATE Request

confirms this: If Connection.Dialect belongs to the SMB 3.x dialect family and Open.LocalOpen is a reparse point, set the SMB2_CREATE_FLAG_REPARSEPOINT bit in the Flags field.

Attached find a network trace against Windows 2016 (build 14393.5648) that seems to behave differently. Frame 14 returns STOPPED_ON_SYMLINK with an unparsed path length of 0. Frame 15 reopens the file with OPEN_REPARSE_POINT. The FileAttributes field in Frame 16 shows this, but the "flags" field according to [ms-smb2] 2.2.14 is 0.

Can you explain if my interpretation of [ms-smb2] is wrong?



More information about the cifs-protocol mailing list