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

Obaid Farooqi obaidf at microsoft.com
Fri Nov 18 18:17:18 UTC 2022

Hi Volker:
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.

Obaid Farooqi
Escalation Engineer | Microsoft

-----Original Message-----
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

Hello dochelp,

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

https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fopenspecs%2Fwindows_protocols%2Fms-fsa%2F41f3734a-5bba-4c3b-9d04-7baafc9b7bfe&data=05%7C01%7Cobaidf%40microsoft.com%7Cc0811c9d84b44da9bfbc08dac967b8da%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638043744581443875%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RHgbMJUT8yOJrqqgojevP2FcCEku8lPmSWGeE3xl2IE%3D&reserved=0 Open of an Existing File

but I did not find it there.

Is it somewhere else defined?



More information about the cifs-protocol mailing list