[cifs-protocol] [EXTERNAL] Re: SMB2_CREATE error code IO_REPARSE_TAG_NOT_HANDLED? - TrackingID#2211180040005873

[Jeff McCashland (He/him)]

Hi Volker,

Thank you for the additional information and trace. I will file a request to update the spec, and follow up on the request. 

Please let us know at our DocHelp alias if you find additional issues with the documentation. 

Best regards,
Jeff McCashland (He/him) | Senior Escalation Engineer | Microsoft Protocol Open Specifications Team 
Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00) Pacific Time (US and Canada)
Local country phone number found here: http://support.microsoft.com/globalenglish | Extension 1138300

-----Original Message-----
From: Volker Lendecke <Volker.Lendecke at sernet.de> 
Sent: Wednesday, November 23, 2022 4:46 AM
To: Jeff McCashland (He/him) <jeffm at microsoft.com>
Cc: cifs-protocol at lists.samba.org; Microsoft Support <supportmail at microsoft.com>
Subject: [EXTERNAL] Re: SMB2_CREATE error code IO_REPARSE_TAG_NOT_HANDLED? - TrackingID#2211180040005873

Hi Jeff,

Am Fri, Nov 18, 2022 at 07:50:29PM +0000 schrieb Jeff McCashland (He/him):
> Have you seen this error over the wire 'in the wild'?
> IO_REPARSE_TAG_LX_CHR is documented in [MS-FSCC] as 'not meaningful 
> over the wire', so artificially creating a 'bogus' reparse point in 
> this manner might be considered a violation of protocol. We don't 
> generally document the results of protocol violations.

here is an example of this "in the wild". I installed the NFS server on Windows 2016, and with frame 53 I did a "ln -s x y" over a NFS mount from Linux. Then in frame 83 I tried to read the attributes of "y" and got the REPARSE_TAG_NOT_HANDLED error message.

I don't think any of this is a protocol violation, so I think this needs to be documented.

Thanks,

Volker