You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I didn't find related section where this package belongs, please ignore and close this if it's not relevant. Also if you can point me to the right direction.
What version of Go are you using (go version)?
go version go1.17.8 linux/amd64
Does this issue reproduce with the latest release?
Didn't try with 1.18
What operating system and processor architecture are you using (go env)?
It would be nice if I get an error if the particular device isn't available.
What did you see instead?
I got an uninterruptible sleep in case of the device determined in the address isn't available.
$ px aux | grep go-build85
XXX 35538 0.0 0.0 703112 1676 pts/2 D 10:59 0:00 /tmp/go-build851823850/b001/exe/main
$ sudo kill -9 35538
$ px aux | grep go-build85
XXX 35538 0.0 0.0 703112 1676 pts/2 D 10:59 0:00 /tmp/go-build851823850/b001/exe/main
The text was updated successfully, but these errors were encountered:
ianlancetaylor
changed the title
golang.org/x/sys/unix: unix.Connect cause uninterruptible sleep
x/sys/unix: unix.Connect cause uninterruptible sleep
Apr 14, 2022
All the Go code is doing is making the system call. If the process locks up and becomes immune to SIGKILL, that sounds like a kernel bug. There is nothing that Go can do to become immune to SIGKILL.
I imagine that the same thing would happen for an equivalent C program.
I'm going to close this because I don't think there is anything we can change in Go to affect this. Please comment if you disagree.
I didn't find related section where this package belongs, please ignore and close this if it's not relevant. Also if you can point me to the right direction.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Didn't try with 1.18
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
It would be nice if I get an error if the particular device isn't available.
What did you see instead?
I got an uninterruptible sleep in case of the device determined in the address isn't available.
The text was updated successfully, but these errors were encountered: