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
runtime: lock ordering problem
between trace
and wbufSpans
#56554
Comments
I still plan to look into this. |
Oh no. This is real. You can't actually have a write barrier while holding |
It seems the write barrier is https://cs.opensource.google/go/go/+/release-branch.go1.20:src/runtime/trace.go;l=535 (Note: I used 1.20 release branch to point to old code). That code is gone with your CL https://golang.org/cl/496296 . So it is probably fixed. |
Thanks for digging it up. I tried the 1.20 release branch but couldn't find it; probably a misclick and I was on the wrong branch in the end. Anyway, yes! Indeed, looks like this problem is solved on tip. |
Found new dashboard test flakes for:
2023-10-25 19:47 linux-amd64-staticlockranking go@a57c5736 runtime/trace.TestTraceFutileWakeup (log)
|
I think this is fixed as of the new tracer, and a bunch of the recent staticlockranking fixes for it. |
https://build.golang.org/log/af083d40156b011db2e0cadd6040692cf579967c:
(attn @golang/runtime)
The text was updated successfully, but these errors were encountered: