You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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
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.
The text was updated successfully, but these errors were encountered: