Hi,Tridge, After reviewing your question with development team and test suite team, we reached the conclusion that the test S46 in SMB2 test suite needs to be changed to accept STATUS_INVALID_DEVICE_REQUEST error code and pass the test. The related windows behavior should not be considered normative and the documentation doesn't need to be changed.
Please let us know if you have further questions. Thanks ---------------------------------------------------------- Hongwei Sun - Support Escalation Engineer DSC Protocol Team, Microsoft [EMAIL PROTECTED] Tel: 469-7757027 x 57027 ----------------------------------------------------------- -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, June 06, 2008 7:35 PM To: Interoperability Documentation Help Cc: [EMAIL PROTECTED] Subject: [cifs-protocol] S46 test - should ioctl invalid code error code be in spec? Hi, At the plugfest this week we ran the WSPP SMB2 tests, and in test S46 Samba4 failed as we returned STATUS_FS_DRIVER_REQUIRED and we failed the test as it was looking for STATUS_INVALID_DEVICE_REQUEST. In the spreadsheet describing the tests, it says that this behaviour is normative, and comes from section 3.3.5.15. If you look in 3.3.5.15 then you'll see that it lists the error code as coming from the object store, and only lists the STATUS_INVALID_DEVICE_REQUEST as being "windows behaviour" in the WB parts of the spec. So perhaps this windows behaviour should now be considered normative and moved into 3.3.3.15 ? Cheers, Tridge _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
