Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with SMBD test cases Smb2OverRdma_Read/Write_SMB2_CHANNEL_RDMA_V1 #211

Closed
vinitagnihotri opened this issue Nov 26, 2019 · 3 comments
Closed
Assignees

Comments

@vinitagnihotri
Copy link

We are running SMBD server equivalent in centos enviroment. While running this
Smb2OverRdma_Read_SMB2_CHANNEL_RDMA_V1 and
Smb2OverRdma_Write_SMB2_CHANNEL_RDMA_V1

we see test suite sends out SMB2_CHANNEL_RDMA_V1_INVALIDATE to which our server responds with "SMB_STATUS_NOT_SUPPORTED" as we do not support as of now.

However test case documentation for this case does not mention this. There are already cases which are specifically meant for invalidation in smb302 group.

Since this is clearly SMB2_CHANNEL_RDMA_V1, it should not send SMB2_CHANNEL_RDMA_V1_INVALIDATE requests. So "SMB_STATUS_NOT_SUPPORTED" should be a considered as valid test result.

@huiren-jiang
Copy link

Hi vinitagnihotri,

Thanks for reporting this issue.

You are right. CHANNEL_RDMA_V1_INVALIDATE should be changed to CHANNEL_RDMA_V1 for write operation of test case Smb2OverRdma_Read_SMB2_CHANNEL_RDMA_V1. We will fix it later and notify you when it is committed to staging.

Best Regards,

Windows Protocol Test Suites Development Team

@huiren-jiang
Copy link

Hi vinitagnihotri,

The fix is available on staging by commit 8894ebd.

Here I attach a signed build with fix MS-SMBD-TestSuite-ServerEP.msi.zip. You could uninstall the old, then try this one to verify the fix.

Best Regards,

Windows Protocol Test Suites Development Team

@yazeng
Copy link
Member

yazeng commented Jan 6, 2020

Hi vinitagnihotri,
Since this thread has been inactive for a long time, we close it for now. Feel free to reopen it if the problem remains.
Windows Protocol Test Suites Development Team

@yazeng yazeng closed this as completed Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants