Skip to content

Support pipe message read mode#82

Merged
jstarks merged 3 commits intomicrosoft:masterfrom
jstarks:pipe_message_mode
Jun 25, 2018
Merged

Support pipe message read mode#82
jstarks merged 3 commits intomicrosoft:masterfrom
jstarks:pipe_message_mode

Conversation

@jstarks
Copy link
Copy Markdown
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
Copy Markdown
Member Author

jstarks commented Jun 25, 2018

This supersedes #78.

@gdamore
Copy link
Copy Markdown
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
Copy Markdown
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
Copy Markdown
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