[ppc64el] external kernel module builds fail looking for missing crtsavres.o

Bug #1318848 reported by Steve Beattie
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Andy Whitcroft
Trusty
Medium
Andy Whitcroft
Utopic
Medium
Andy Whitcroft

Bug Description

Attempting build even a simple hello world kernel on ppc64el fails with the following error:

  /usr/bin/ld.bfd.real: cannot find arch/powerpc/lib/crtsavres.o: No such file or directory

To reproduce, the Hello World kernel module from http://tldp.org/LDP/lkmpg/2.6/html/x121.html#AEN128 , using it and the Makefile at http://tldp.org/LDP/lkmpg/2.6/html/x181.html#AEN189 , gives the following result:

  $ make
  make -C /lib/modules/3.13.0-24-generic/build M=/home/sbeattie/tmp/hello modules
  make[1]: Entering directory `/usr/src/linux-headers-3.13.0-24-generic'
    CC [M] /home/sbeattie/tmp/hello/hello-1.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /home/sbeattie/tmp/hello/hello-1.mod.o
    LD [M] /home/sbeattie/tmp/hello/hello-1.ko
  /usr/bin/ld.bfd.real: cannot find arch/powerpc/lib/crtsavres.o: No such file or directory
  make[2]: *** [/home/sbeattie/tmp/hello/hello-1.ko] Error 1
  make[1]: *** [modules] Error 2
  make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-24-generic'
  make: *** [all] Error 2

A similar build failure is reproduced with the test-kernel-security.py:test_072_strict_devmem() test failure from the lp:qa-regression-testing tree.

Seen with 3.13.0-24.46 and 3.13.0-24.47.

CVE References

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1318848

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: trusty
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Andy Whitcroft (apw) wrote :

Ok we have a specific bit of code for powerpc builds for this, it seems that needs to trigger for pp64el as well, or more correctly for build_arch powerpc. Will sort and propose a patch to kernel_team@.

Changed in linux (Ubuntu):
assignee: nobody → Andy Whitcroft (apw)
Andy Whitcroft (apw)
Changed in linux (Ubuntu Trusty):
assignee: nobody → Andy Whitcroft (apw)
status: New → Confirmed
Changed in linux (Ubuntu Utopic):
importance: Undecided → Medium
Changed in linux (Ubuntu Trusty):
importance: Undecided → Medium
Changed in linux (Ubuntu Utopic):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 3.15.0-1.5

---------------
linux (3.15.0-1.5) utopic; urgency=low

  [ Tim Gardner ]

  * [Config] Add apm-mustang.dtb to kernel-image udeb
 -- Tim Gardner <email address hidden> Mon, 19 May 2014 14:47:42 -0700

Changed in linux (Ubuntu Utopic):
status: Fix Committed → Fix Released
Revision history for this message
Luis Henriques (henrix) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!
jk

tags: added: verification-needed-trusty
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 3.13.0-29.53

---------------
linux (3.13.0-29.53) trusty; urgency=low

  [ Upstream Kernel Changes ]

  * futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr ==
    uaddr2 in futex_requeue(..., requeue_pi=1)
    - LP: #1326367
    - CVE-2014-3153
  * futex: Validate atomic acquisition in futex_lock_pi_atomic()
    - LP: #1326367
    - CVE-2014-3153
  * futex: Always cleanup owner tid in unlock_pi
    - LP: #1326367
    - CVE-2014-3153
  * futex: Make lookup_pi_state more robust
    - LP: #1326367
    - CVE-2014-3153
 -- Brad Figg <email address hidden> Wed, 04 Jun 2014 08:25:41 -0700

Changed in linux (Ubuntu Trusty):
status: Confirmed → Fix Released
Revision history for this message
Steve Beattie (sbeattie) wrote :

I've verified this was fixed in 3.13.0-29.53. Thanks!

tags: added: verification-done-trusty
removed: verification-needed-trusty
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers