arm64: "unsupported RELA relocation"
Bug #1533009 reported by
dann frazier
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro GCC |
Unknown
|
Unknown
|
|||
Linux |
Unknown
|
Unknown
|
|||
gcc-5 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Trusty |
New
|
Undecided
|
Unassigned | ||
Vivid |
New
|
Undecided
|
Unassigned | ||
Wily |
New
|
Undecided
|
Unassigned | ||
Xenial |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
High
|
Paolo Pisati | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
Vivid |
Fix Released
|
Undecided
|
Unassigned | ||
Wily |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Paolo Pisati |
Bug Description
linux-image-
[ 2.156817] module libahci: unsupported RELA relocation: 275
This is reminiscent of LP: #1502946 - except that fix appears to still be in-tact. What has changed, however, is the build environment. If I rebuild the same kernel source in a wily chroot, it boots fine.
Marking "Confirmed" because Paulo Pisatti reported this to me, and I reproduced.
Related branches
CVE References
tags: | added: hs-arm64 |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
Changed in linux (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in linux (Ubuntu Xenial): | |
assignee: | nobody → Paolo Pisati (p-pisati) |
status: | Triaged → Fix Committed |
Changed in gcc-5 (Ubuntu Xenial): | |
status: | Confirmed → Invalid |
Changed in linux (Ubuntu Trusty): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Wily): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Vivid): | |
status: | New → Fix Committed |
To post a comment you must log in.
When I built 4.3.0-7-generic on arm64(mustang) Wily with the following steps,
fakeroot debian/rules clean
fakeroot debian/rules binary-generic
by this compiler:
ubuntu@ubuntu:~$ gcc -v LTO_WRAPPER= /usr/lib/ gcc/aarch64- linux-gnu/ 5/lto-wrapper pkgversion= 'Ubuntu bugurl= file:// /usr/share/ doc/gcc- 5/README. Bugs languages= c,ada,c+ +,java, go,d,fortran, objc,obj- c++ linker- build-id --libexecdir= /usr/lib included- gettext --enable- threads= posix --libdir=/usr/lib clocale= gnu libstdcxx- debug --enable- libstdcxx- time=yes default- libstdcxx- abi=new --enable- gnu-unique- object libquadmath --enable-plugin --with-system-zlib browser- plugin --enable- java-awt= gtk --enable-gtk-cairo java-home= /usr/lib/ jvm/java- 1.5.0-gcj- 5-arm64/ jre jvm-root- dir=/usr/ lib/jvm/ java-1. 5.0-gcj- 5-arm64 jvm-jar- dir=/usr/ lib/jvm- exports/ java-1. 5.0-gcj- 5-arm64 arch-directory= aarch64 ecj-jar= /usr/share/ java/eclipse- ecj.jar --enable-multiarch checking= release --build= aarch64- linux-gnu aarch64- linux-gnu --target= aarch64- linux-gnu
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_
Target: aarch64-linux-gnu
Configured with: ../src/configure -v --with-
5.2.1-22ubuntu2' --with-
--enable-
--prefix=/usr --program-suffix=-5 --enable-shared
--enable-
--without-
--enable-nls --with-sysroot=/ --enable-
--enable-
--with-
--disable-
--disable-
--with-
--enable-java-home
--with-
--with-
--with-
--with-
--disable-werror --enable-
--host=
the built image just works well:
ubuntu@ ubuntu: ~$ uname -a
Linux ubuntu 4.3.0-7-generic #18 SMP Tue Jan 12 10:19:24 EST 2016
aarch64 aarch64 aarch64 GNU/Linux
But I can see the issue when booting a kernel from the following package[1]:
http:// launchpadlibrar ian.net/ 230287220/ linux-image- 4.3.0-5- generic_ 4.3.0-5. 16_arm64. deb
It is a build environment issue instead of kernel issue, please see
comments from Ard Biesheuvel <email address hidden> [2]:
RELA #275 is the relocation against ADRP instructions, which GCC
should not emit anymore when -mcmodel=large is in effect.
Can you confirm that the modules have been rebuilt with this config as
R_AARCH64_ ADR_PREL_ PG_HI21 relocations?
well? Can you double check the GCC command line (with V=1) when doing
'make modules' to ensure that '-mcmodel=large' is being passed? Can
you check with 'readelf -r' which objects still contain
I have checked the gcc flag in my building environment, and '-mcmodel=large' is ARM64_ERRATUM_ 843419 is enabled too.
passed, and CONFIG_
I don't know how the image in [1] is built, so could anyone check the build
environment for this building?
[1] http:// launchpadlibrar ian.net/ 230287220/ linux-image- 4.3.0-5- generic_ 4.3.0-5. 16_arm64. deb www.spinics. net/lists/ arm-kernel/ msg449991. html
[2] http://
On Tue, Jan 12, 2016 at 7:47 PM, Raghuram Kota /bugs.launchpad .net/bugs/ 1533009 4.3.0-5- generic 4.3.0-5.16 arm64 fails to lo...
<email address hidden> wrote:
> ** Tags added: hs-arm64
>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https:/
>
> Title:
> arm64: "unsupported RELA relocation"
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> linux-image-