[arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gcc |
Unknown
|
Unknown
|
|||
gcc-5 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
gccgo-4.9 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
Vivid |
Invalid
|
Undecided
|
Unassigned | ||
Wily |
Invalid
|
Undecided
|
Unassigned | ||
gccgo-5 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Vivid |
Fix Released
|
Undecided
|
Unassigned | ||
juju-core (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Various go-based packages crash on startup on arm64 when booted with a kernel where CONFIG_
Ubuntu does not ship with this config, so it is currently not impacted. However, we would like to enable this config to add new hardware support in 15.10. The 15.10 kernel will eventually be provided in trusty as an lts backport, at which point this will begin to break users.
[Test Case]
Boot an arm64 system with CONFIG_
[Regression Risk]
The risk of regression is lessened by testing this release on existing Ubuntu kernels w/ 3 level page tables.
CVE References
tags: | added: hs-arm64 |
tags: | added: arm64 |
summary: |
- [arm64] lxd crashes on startup + [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4 |
affects: | lxd (Ubuntu) → gcc-4.9 (Ubuntu) |
Changed in gcc-4.9 (Ubuntu): | |
status: | New → Confirmed |
Changed in gcc-4.8 (Ubuntu): | |
status: | New → Confirmed |
Changed in gcc-4.8 (Ubuntu Trusty): | |
status: | New → Confirmed |
no longer affects: | gcc-4.8 (Ubuntu) |
no longer affects: | gcc-4.9 (Ubuntu) |
Changed in gccgo-4.9 (Ubuntu Trusty): | |
status: | New → Confirmed |
Changed in gcc-4.8 (Ubuntu Trusty): | |
status: | Confirmed → New |
Changed in gcc-4.8 (Ubuntu Wily): | |
status: | Confirmed → New |
no longer affects: | gcc-4.8 (Ubuntu Trusty) |
no longer affects: | gcc-4.8 (Ubuntu Wily) |
no longer affects: | gcc-4.8 (Ubuntu Vivid) |
no longer affects: | gcc-4.9 (Ubuntu Trusty) |
no longer affects: | gcc-4.9 (Ubuntu Vivid) |
no longer affects: | gcc-4.9 (Ubuntu Wily) |
no longer affects: | gccgo-5 (Ubuntu Trusty) |
no longer affects: | gccgo-5 (Ubuntu Wily) |
Changed in gccgo-4.9 (Ubuntu Vivid): | |
status: | New → In Progress |
Changed in gccgo-4.9 (Ubuntu Trusty): | |
status: | Confirmed → Invalid |
status: | Invalid → In Progress |
Changed in gccgo-4.9 (Ubuntu Vivid): | |
status: | In Progress → Invalid |
Changed in gccgo-4.9 (Ubuntu Wily): | |
status: | New → Invalid |
Changed in gccgo-5 (Ubuntu Vivid): | |
status: | New → In Progress |
Changed in gccgo-5 (Ubuntu): | |
status: | New → Invalid |
description: | updated |
This issue persists with lxd 0.13-0ubuntu1. Note that it doesn't fail on all arm64 systems, but failures seems to be correlated w/ a high core count.