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
Does this issue reproduce with the latest release?
not
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
darwin arm64
What did you do?
There might be a potential safety problem about the variable of err in :https://github.com/golang/go/blob/master/src/net/http/transport.go#L1707
I am not sure if it's right. This variable can be accessed in two different goroutines, but without any mutex or other concurrent protection.
I have seen the didReadResponse chan so that it can guarantee the sequence of two goroutines. But I am not sure that if err variable will and must get the result of another goroutine. Will CPU cache affect it?
According to the The Go Memory Model: https://go.dev/ref/mem. Thanks.
What did you expect to see?
Confirmed that if it has a potential safety problem.
What did you see instead?
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
not
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
There might be a potential safety problem about the variable of err in :https://github.com/golang/go/blob/master/src/net/http/transport.go#L1707
I am not sure if it's right. This variable can be accessed in two different goroutines, but without any mutex or other concurrent protection.
I have seen the didReadResponse chan so that it can guarantee the sequence of two goroutines. But I am not sure that if err variable will and must get the result of another goroutine. Will CPU cache affect it?
According to the The Go Memory Model: https://go.dev/ref/mem. Thanks.
What did you expect to see?
Confirmed that if it has a potential safety problem.
What did you see instead?
The text was updated successfully, but these errors were encountered: