Skip to content

runtime: incorrect frame information in traceback traversal may hang the process. [1.16 backport] #50780

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.

Sign up for GitHub

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

Jump to bottom
Closed
gopherbot opened this issue Jan 24, 2022 · 3 comments
Closed

runtime: incorrect frame information in traceback traversal may hang the process. [1.16 backport] #50780

gopherbot opened this issue Jan 24, 2022 · 3 comments
Labels
CherryPickApproved Used during the release process for point releases FrozenDueToAge
Milestone
Go1.16.14

Comments

@gopherbot
Copy link
Contributor

@cherrymui requested issue #50772 to be considered for backport to the next 1.16 minor release.

@gopherbot please backport this to previous releases. This may cause programs to hang. Thanks.
@gopherbot gopherbot added the CherryPickCandidate Used during the release process for point releases label Jan 24, 2022
@gopherbot gopherbot mentioned this issue Jan 24, 2022
Closed
@gopherbot gopherbot added this to the Go1.16.14 milestone Jan 24, 2022
@gopherbot
Copy link
Contributor Author

Change https://golang.org/cl/380716 mentions this issue: [release-branch.go1.16] runtime: set vdsoSP to caller's SP consistently

@toothrot toothrot added the CherryPickApproved Used during the release process for point releases label Feb 3, 2022
@toothrot
Copy link
Contributor

toothrot commented Feb 3, 2022

Approved. This is a serious issue with no workaround.

@gopherbot gopherbot removed the CherryPickCandidate Used during the release process for point releases label Feb 3, 2022
gopherbot pushed a commit that referenced this issue Feb 7, 2022
@cherrymui
[release-branch.go1.16] runtime: set vdsoSP to caller's SP consistently
e2277c8 
m.vdsoSP should be set to the SP of the caller of nanotime1,
instead of the SP of nanotime1 itself, which matches m.vdsoPC.
Otherwise the unmatched vdsoPC and vdsoSP would make the stack
trace look like recursive.

We already do it correctly on AMD64, 386, and RISCV64. This CL
fixes the rest.

Also incorporate CL 352509, skipping a flaky test.

Updates #47324, #50772.
Fixes #50780.

Change-Id: I98b6fcfbe9fc6bdd28b8fe2a1299b7c505371dd4
Reviewed-on: https://go-review.googlesource.com/c/go/+/337590
Trust: Cherry Mui <[email protected]>
Trust: Josh Bleecher Snyder <[email protected]>
Reviewed-by: Josh Bleecher Snyder <[email protected]>
(cherry picked from commit 217507e)
Reviewed-on: https://go-review.googlesource.com/c/go/+/380716
Run-TryBot: Cherry Mui <[email protected]>
TryBot-Result: Gopher Robot <[email protected]>
Reviewed-by: Michael Knyszek <[email protected]>
@gopherbot
Copy link
Contributor Author

Closed by merging e2277c8 to release-branch.go1.16.

@golang golang locked and limited conversation to collaborators Feb 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
CherryPickApproved Used during the release process for point releases FrozenDueToAge
Projects
None yet
Milestone
Go1.16.14
Development

No branches or pull requests
2 participants
@toothrot @gopherbot