-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: "attempt to execute system stack code on user stack" during heap scavenging [1.13 backport] #36127
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
Comments
@mknyszek, would you mind preparing a quick backport CL for this? |
Sorry! Slipped under my radar. On it. |
Change https://golang.org/cl/212103 mentions this issue: |
Approving this for Go 1.13 because it is a serious problem (programs may crash when certain rare conditions are met) without a workaround. The fix is small. This does not need to be backported to Go 1.12 as well because it is not an issue on that release branch. |
…d of ready This changes fixes an oversight in wakeScavenger which would cause ready to be called off of the system stack. This change makes it so that wakeScavenger calls goready, which switches to the system stack before calling ready. Fixes #36127. Change-Id: Icb13f180b4d8fdd47c921eac1b896e3dd49e43b3 Reviewed-on: https://go-review.googlesource.com/c/go/+/200999 Run-TryBot: Michael Knyszek <[email protected]> Reviewed-by: Keith Randall <[email protected]> (cherry picked from commit 2c87be4) Reviewed-on: https://go-review.googlesource.com/c/go/+/212103 TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Austin Clements <[email protected]>
Closed by merging b0a2a81 to release-branch.go1.13. |
@aclements requested issue #34773 to be considered for backport to the next 1.13 minor release.
The text was updated successfully, but these errors were encountered: