On Tue, Jan 19, 2016 at 2:24 PM, Christophe Lyon
<email address hidden> 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:~$
On Tue, Jan 19, 2016 at 2:24 PM, Christophe Lyon
<email address hidden> 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 OVERLAY_ FS=m" >> .config
cd linux-4.3.3
make defconfig
# enable simple module for testing
echo "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:~$