initrd.img symlink is created absolute when the initrd creation is delayed

A candidate fix is to pass the vmlinuz-3.11.0-12-generic (or whatever) filename into the test_relative() function for the 'Test File' parameter, when it's called for the non-existent initrd.img-* file, since the vmlinuz is guaranteed to be present.

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

apport-collect 1248053

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.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Just for the record, viewing the report data crashed apport-collect:

root@zbox:~# apport-collect 1248053
...
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
..dpkg-query: no packages found matching linux
.......

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (972.0 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): v
Traceback (most recent call last):
  File "/usr/bin/apport-cli", line 367, in <module>
    if not app.run_argv():
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 656, in run_argv
    return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 572, in run_update_report
    response = self.ui_present_report_details(allowed_to_report)
  File "/usr/bin/apport-cli", line 206, in ui_present_report_details
    self.collect_info()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 969, in collect_info
    if self.report['ProblemType'] == 'Crash':
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
    raise KeyError(key)
KeyError: 'ProblemType'

@Daniel -- that 'V' view bug should be reported against apport, that is rather, sad.

I think you are saying that if the file already exists then the linking code will emit a non-absolute link, if it is missing then an absolute one. I think this is born out by my system which clearly has a reinstalled kernel at the same version on it:

lrwxrwxrwx 1 root root 32 Nov 4 18:45 initrd.img -> boot/initrd.img-3.8.0-32-generic
lrwxrwxrwx 1 root root 33 Nov 4 18:45 initrd.img.old -> /boot/initrd.img-3.8.0-32-generic

The first one (.old) would have not had an initrd in place when linking the other would.

This actually occurs because test_relative() as used in the really_move_link() call will fail as the destination file actually does not exist, triggering a failure in that incantation. This also highlights we are going to incorrectly indicate that the link is dandling in the case of installing linux-image and linux-image-extra at the same time.

I don't think it's directly related, but I also see the umask not being consistent:

$ ls -l boot/
total 42968
-rw-r--r-- 1 root root 1005798 Oct 10 00:49 abi-3.11.0-12-generic
-rw-r--r-- 1 root root 1003704 Nov 4 08:44 abi-3.12.0-031200-generic
-rw-r--r-- 1 root root 163251 Oct 10 00:49 config-3.11.0-12-generic
-rw-r--r-- 1 root root 162643 Nov 4 08:44 config-3.12.0-031200-generic
-rw-r--r-- 1 root root 11724654 Nov 4 10:13 initrd.img-3.11.0-12-generic
-rw-r--r-- 1 root root 11768349 Nov 5 19:50 initrd.img-3.12.0-031200-generic
-rw-r--r-- 1 root root 3285893 Oct 10 00:49 System.map-3.11.0-12-generic
-rw------- 1 root root 3466224 Nov 4 08:44 System.map-3.12.0-031200-generic
-rw-r--r-- 1 root root 5600016 Oct 10 00:49 vmlinuz-3.11.0-12-generic
-rw------- 1 root root 5793312 Nov 4 08:44 vmlinuz-3.12.0-031200-generic

I can log this as a separate issue, though what package should it be against if it's the mainline kernel, as we see here?

@Daniel -- which bit is inconsistent. I would expect, and see on my kit, that the abi and config are 644 and System.map and vmlinuz are 600 consistently across the board. The mainline ones in your case seem to be so also. I am assuming you have modified the others yourself.

Ok fixed both of these issues and pushed the fixes to Trusty for testing. Will be in the next upload there.

This bug was fixed in the package linux - 3.12.0-2.5

---------------
linux (3.12.0-2.5) trusty; urgency=low

  [ Andy Whitcroft ]

  * rebase to mainline v3.12
  * [Config] updateconfigs following rebase to v3.12
  * postinst -- improve relative symlink detection with missing files
    - LP: #1248053
  * postinst -- fix unchanged link detection
  * [Config] update configs following addition of apparmor fixes

  [ Anthony Wong ]

  * SAUCE: Work around broken ACPI backlight on Dell Inspiron 5537
    - LP: #1231305

  [ John Johansen ]

  * SAUCE: (no-up) apparmor: Sync to apparmor 3 - alpha 4 snapshot
  * SAUCE: apparmor: fix unix domain sockets to be mediated on connection
    - LP: #1208988
  * SAUCE: apparmor: allocate path lookup buffers during init
    - LP: #1208988

  [ Tim Gardner ]

  * [Config] Remove superfluous ubuntu/lttng-modules

  [ Upstream Kernel Changes ]

  * Revert "fork: unify and tighten up CLONE_NEWUSER/CLONE_NEWPID checks"
    - LP: #1248590

  [ Upstream Kernel Changes ]

  * rebase to v3.12
    - LP: #1222850

  [ Adam Conrad ]
  * etc/getabis: Fetch arm64/generic abis as well
 -- Andy Whitcroft <email address hidden> Wed, 06 Nov 2013 21:00:21 +0000

This bug was nominated against a series that is no longer supported, ie saucy. The bug task representing the saucy nomination is being closed as Won't Fix.

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