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
net/http: Data race in net/http in 1.10.3 [1.10 backport] #27129
Comments
CL is https://golang.org/cl/96575 . |
Change https://golang.org/cl/95775 mentions this issue: |
People also were concerned about the performance hit which https://golang.org/cl/113996 mitigated. |
@LK4D4, we do not backport performance changes. People can move forward to Go 1.11 if they want new goodies. |
Closed by merging ba5e308 to release-branch.go1.10. |
…edirect Since that method uses `mux.m`, we need to lock the mutex to avoid data races. Fixes #27129 Change-Id: I998448a6e482b5d6a1b24f3354bb824906e23172 Reviewed-on: https://go-review.googlesource.com/95775 Reviewed-by: Andrew Bonventre <andybons@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
What version of Go are you using (
go version
)?go1.10.3
Does this issue reproduce with the latest release?
No
What did you do?
The race is between ServerMux.Handle and ServerMux.Handler, but it was fixed in 2fd1b52
I just want to be sure that it'll be backported to 1.10.4, because it makes continuous race detection hard and also race is fatal because it's between map read and write.
The text was updated successfully, but these errors were encountered: