-
Notifications
You must be signed in to change notification settings - Fork 18k
net, syscall: a race condition caused by syscall.SocketDisableIPv6 #7687
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
Labels
Milestone
Comments
CL https://golang.org/cl/108930044 mentions this issue. |
I don't understand the race here. Presumably TestDialDualStackLocahost runs and completes before TestDialGoogleIPv4 starts. Why is the read during TestDialDualStackLocahost not seen as happening before the write in TestDialGoogleIPv4? Is TestDialDualStackLocahost leaving a background goroutine running that it should not? |
TestDialDualStackLocahost uses net.Dialer{DualStack: true} so that it tests ipv4-only, ipv6-only and dual ipv{4,6} cases, and it leaves the looser dial goroutine until the kernel gives up to attempt 3-way handshaking. Would you prefer to introduce syscall.Connect cancelleration stuff in go1.5? Though I`m wondering why we still need syscall.SocketDisableIPv6. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: