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

Support pipe message read mode #82

Merged
merged 3 commits into from
Jun 25, 2018
Merged

Conversation

jstarks
Copy link
Member

@jstarks jstarks commented Jun 25, 2018

Message read mode is the only read mode supported for vSMB named pipes, which are used to provide named pipe mapping for Hyper-V-isolated Windows containers. Transparently support this mode.

@jstarks
Copy link
Member Author

jstarks commented Jun 25, 2018

This supersedes #78.

@gdamore
Copy link
Contributor

gdamore commented Jun 25, 2018

I like this approach. Now I think maybe I should take care to ensure that message read mode is supported in my C code that deals with named pipes .

Copy link
Member

@johnstep johnstep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

I verified this on Windows 1803 and it works as expected.

It would have been nice to have the test ensure that DialPipe accepts message-read mode, but it appears that pipe clients returned by CreateFile are always in byte-read mode initially (per https://msdn.microsoft.com/en-us/library/windows/desktop/aa365605(v=vs.85).aspx), except for vSMB named pipes, making that very difficult to verify from a unit test.

@jstarks jstarks merged commit 6792112 into microsoft:master Jun 25, 2018
@thaJeztah
Copy link
Contributor

@jstarks is it possible to tag a new release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants