-
Notifications
You must be signed in to change notification settings - Fork 822
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
socketpair() syscall ignores non-blocking request (SOCK_NONBLOCK, O_NONBLOCK) #3100
Comments
Mention Windows build version. |
@Biswa96 added. thx! |
Rare; +1 (I was loosing faith). Not even sure it is a dupe (too hard to search). |
That is why I am dog-clear in subject and description, including example-code to reproduce. No other ticket came close to it, that's why I created a dedicated one. |
It's #2949, I think (right?). Don't quibble on the flags. Won't dupe ya. |
This should be fixed in build 17666. |
This was referenced Sep 11, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
(windows version: 10.0.17133.73)
I found out that the syscall
socketpair
is litereally ignoring theSOCK_NONBLOCK
argument.Also is
fcntl
's attempt to makesocketpair
's sockets non-blocking ignored.Here's a minimal example program that proofs both cases. On original Linux it immediately quits as expected with the appropriate error message (
EAGAIN
), but on WSL/Linux it freezes after having filled one end with163840
bytes.The text was updated successfully, but these errors were encountered: