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 tip after CL 461675 #60041
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
release-blocker
Milestone
Comments
@neild do you have an opinion on whether this is a release blocker? Getting very close to the freeze and RC now. |
Change https://go.dev/cl/496016 mentions this issue: |
Don't know if it's a release blocker, but I believe I have a fix. |
Change https://go.dev/cl/496335 mentions this issue: |
gopherbot
pushed a commit
to golang/net
that referenced
this issue
May 24, 2023
When returning an error from RoundTrip, wait for the close of the request body to complete before returning. This avoids a race between the HTTP/2 transport closing the request body and the net/http retry loop examining the readTrackingBody to see if it has been closed. For golang/go#60041 Change-Id: I8be69ff5056806406716e01e02d1f631deeca088 Reviewed-on: https://go-review.googlesource.com/c/net/+/496335 Run-TryBot: Damien Neil <dneil@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
release-blocker
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Go 1.20.x: no
Tip: yes
What operating system and processor architecture are you using (
go env
)?darwin
What did you do?
What did you expect to see?
Test pass
What did you see instead?
I believe I have bisected it to this change, #49621, which introduce the type assertion to
req.Body.(*readTrackingBody)
which elides the read body lock./cc @bradfitz @neild
The text was updated successfully, but these errors were encountered: