Go runtime: ppc64x binaries randomly segfault on linux 5.13rc6 (#46803)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
Undecided
|
Ubuntu on IBM Power Systems Bug Triage | ||
golang (Ubuntu) |
Fix Released
|
Undecided
|
bugproxy |
Bug Description
https:/
(https:/
This seems to be a somehow older issue, since we noticed this discussion on 5.11:
https://<email address hidden>/
“
Issue where the 5.13 kernel makes binaries built with Go before 1.15.15, 1.16.7, 1.17 prone to crashing when they receive a signal. The upstream bug report is here https:/
We made sure that everything works on Impish and rebuilt all Go binaries - so impish (and newer) is fine; since for impish we added the above kernel patch (the one discussed in the lkml) to our Ubuntu kernel 5.13.0-16.16:
fe57d86f7c3f ("powerpc/vdso: Don't use r30 to avoid breaking Go lang")
But we are still a bit concerned about older kernels / potential backports needed,
since this could be an issue with running older containers on newer hosts, and it potentially can be an issue for snaps, too.
affects: | libpmemobj-cpp (Ubuntu) → golang (Ubuntu) |
Changed in ubuntu-power-systems: | |
assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
Changed in golang (Ubuntu): | |
assignee: | nobody → bugproxy (bugproxy) |
Changed in ubuntu-power-systems: | |
status: | New → Opinion |
Changed in golang (Ubuntu): | |
status: | New → Opinion |
description: | updated |
tags: | added: ppc64el |
Hirsute/linux (and other v5.11 derivatives) got it as well via stable updates. Kernels older than v5.11 do not have commit switching vDSO to generic implementation (which can touch r30), therefore should not be affected.