kernel-packages team mailing list archive

[dann frazier <dann.frazier@xxxxxxxxxxxxx>]

On Tue, Jan 19, 2016 at 2:24 PM, Christophe Lyon
<christophe.lyon@xxxxxxxxxx> wrote:
> It's not clear to me how I can reproduce the problem as a GCC developper.
> Should I build kernel-4.3.0 (vanilla), using the defconfig attached on comment #13, build the modules and look for the relocation mentioned by Ard Biesheuvel?

Hi Christophe,
  Here's the steps to reproduce (I'm doing this in an Ubuntu
16.04/arm64 QEMU/KVM VM):

tar xfJ linux-4.3.3.tar.xz
cd linux-4.3.3
make defconfig
# enable simple module for testing
echo "CONFIG_OVERLAY_FS=m" >> .config
make oldconfig
make Image modules
sudo make install
sudo reboot

Then, on reboot:

$ sudo dmesg -c > /dev/null
$ sudo modprobe overlay
modprobe: ERROR: could not insert 'overlay': Exec format error
$ dmesg
[  336.449238] module overlay: unsupported RELA relocation: 275
ubuntu@ubuntu:~$

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1533009

Title:
  arm64: "unsupported RELA relocation"

Status in Linaro GCC:
  Unknown
Status in Linux:
  Unknown
Status in gcc-5 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  linux-image-4.3.0-5-generic 4.3.0-5.16 arm64 fails to load modules
  (and therefore boot). It emits messages like the following for each
  attempted module load:

  [    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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-linaro/+bug/1533009/+subscriptions