Skip to content

net: UDP socket close doesn't unblock read in other goroutine #2116

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

Closed
alberts opened this issue Jul 29, 2011 · 12 comments
Closed

net: UDP socket close doesn't unblock read in other goroutine #2116

alberts opened this issue Jul 29, 2011 · 12 comments
Milestone

Comments

@alberts
Copy link
Contributor

alberts commented Jul 29, 2011

What steps will reproduce the problem?
1. Read from udp socket in one goroutine
2. Close socket in another goroutine
3. Read doesn't return

Which compiler are you using (5g, 6g, 8g, gccgo)?

6g

Which operating system are you using?

linux

Which revision are you using?  (hg identify)

tip

Please provide any additional information below.

http://groups.google.com/group/golang-nuts/browse_thread/thread/3d71c119d68a1b4a
@alberts
Copy link
Contributor Author

alberts commented Jul 29, 2011

Comment 1:

If someone starts looking into this, it might also be worth it to sort out Shutdown:
calling shutdown on a UDP socket doesn't make sense (it returns ENOTCONN)
Discussed here:
http://groups.google.com/group/golang-nuts/browse_thread/thread/4cbbc28d5aa7ca52
and here:
http://groups.google.com/group/golang-dev/browse_thread/thread/c6ef223b67936f07

@robpike
Copy link
Contributor

robpike commented Aug 3, 2011

Comment 2:

Owner changed to @rsc.

Status changed to Accepted.

@gopherbot
Copy link
Contributor

Comment 3 by jp@webmaster.ms:

same problem on Windows.

@gopherbot
Copy link
Contributor

Comment 4 by jp@webmaster.ms:

The solution for Windows is http://golang.org/cl/5130041/
Perhaps there is the same issue with unclosed handle on Linux as well.

@rsc
Copy link
Contributor

rsc commented Sep 26, 2011

Comment 5:

codereview/5130041 does not exist?

@gopherbot
Copy link
Contributor

Comment 6 by webmaster@webmaster.ms:

it was a wrong fix, 'http' tests fail with it.

@rsc
Copy link
Contributor

rsc commented Oct 3, 2011

Comment 7:

Issue #2326 has been merged into this issue.

@rsc
Copy link
Contributor

rsc commented Dec 9, 2011

Comment 8:

Labels changed: added priority-later, removed priority-medium.

@rsc
Copy link
Contributor

rsc commented Dec 12, 2011

Comment 9:

Labels changed: added priority-go1.

@robpike
Copy link
Contributor

robpike commented Jan 13, 2012

Comment 10:

Owner changed to builder@golang.org.

@rsc
Copy link
Contributor

rsc commented Feb 12, 2012

Comment 12:

Owner changed to @rsc.

Status changed to Started.

@rsc
Copy link
Contributor

rsc commented Feb 14, 2012

Comment 13:

This issue was closed by revision 5e4e3d8.

Status changed to Fixed.

@rsc rsc added this to the Go1 milestone Apr 10, 2015
@rsc rsc removed the priority-go1 label Apr 10, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
@rsc rsc removed their assignment Jun 22, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants