-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
os: SetDeadline doesn't work after an Fd() call #22934
Labels
Milestone
Comments
Ian, I assume this is also just a documentation thing? |
Change https://golang.org/cl/81636 mentions this issue: |
Change https://golang.org/cl/82915 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Dec 8, 2017
This essentially applies https://golang.org/cl/81636 to the net package. The full truth seems too complicated to write in this method's doc, so I'm going with a simple half truth. The full truth is that File returns the descriptor in blocking mode, because that is historically how it worked, and existing programs would be surprised if the descriptor is suddenly non-blocking. On Unix systems whether a socket is non-blocking or not is a property of the underlying file description, not of a particular file descriptor, so changing the returned descriptor to blocking mode also changes the existing socket to blocking mode. Blocking mode works fine, althoug I/O operations now take up a thread. SetDeadline and friends rely on the runtime poller, and the runtime poller only works if the descriptor is non-blocking. So it's correct that calling File disables SetDeadline. The other half of the truth is that if the program is willing to work with a non-blocking descriptor, it could call syscall.SetNonblock(f.Fd(), true) to change the descriptor, and the original socket, to non-blocking mode. At that point SetDeadline would start working again. I tried to write that in a way that is short and comprehensible but failed. Since we now have the RawConn approach to frobbing the descriptor, and hopefully most people can use that rather than calling File, I decided to punt. Updates #22934 Fixes #21862 Change-Id: If269da762f6f5a88c334e7b6d6f3998f7e10b11e Reviewed-on: https://go-review.googlesource.com/82915 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Go are you using (
go version
)?go version devel +ed8b7dedd3 Thu Nov 30 01:46:50 2017 +0000 linux/amd64
What did you do?
What did you expect to see?
A timeout error.
Or an error when
SetDeadline
.The
Fd()
can also be called afterSetDeadline()
, so a timeout error is better.What did you see instead?
A successful Read and "Hello, world!".
The method
Fd()
put the file descriptor into blocking mode and the deadline doesn't work after it.go/src/os/file_unix.go
Line 68 in 8064f82
There is a similar issue with package
net
. #21862The text was updated successfully, but these errors were encountered: