[cifs-protocol] SMB2_CREATE error code IO_REPARSE_TAG_NOT_HANDLED? - TrackingID#2211180040005873
Jeff McCashland (He/him)
jeffm at microsoft.com
Fri Nov 18 19:05:50 UTC 2022
[Obaid to BCC]
Thank you for bringing this to our attention and providing a network trace. I will file a request to update our documentation as needed.
It may be that this will go into [MS-FSCC].
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
From: Obaid Farooqi <obaidf at microsoft.com>
Sent: Friday, November 18, 2022 10:17 AM
To: Volker.Lendecke at sernet.de
Cc: cifs-protocol at lists.samba.org; Microsoft Support <supportmail at microsoft.com>
Subject: SMB2_CREATE error code IO_REPARSE_TAG_NOT_HANDLED? - TrackingID#2211180040005873
Thanks for contacting Microsoft. I have created a case to track this issue. A member of the open specifications team will be in touch soon.
Escalation Engineer | Microsoft
From: Volker Lendecke <Volker.Lendecke at sernet.de>
Sent: Friday, November 18, 2022 7:21 AM
To: Interoperability Documentation Help <dochelp at microsoft.com>
Cc: cifs-protocol at lists.samba.org
Subject: [EXTERNAL] SMB2_CREATE error code IO_REPARSE_TAG_NOT_HANDLED?
attached find a trace with an error code I can't find in [MS-SMB2] nor in [MS-FSA] in the places I would expect it.
Frame 17 sets bogus reparse point data on a fresh file, and frame 21 tries to delete that file again without the OPEN_REPARSE_POINT create option. It gets NTSTATUS code 0xc0000279, which Samba and Wireshark translate to IO_REPARSE_TAG_NOT_HANDLED. I would expect this error code to be mmentioned in
184.108.40.206.2 Open of an Existing File
but I did not find it there.
Is it somewhere else defined?
More information about the cifs-protocol