Bug #1536810 “kernel install failed /bin/cp: cannot stat ‘/boot/...” : Bugs : linux package : Ubuntu

Revision history for this message

Scott Moser (smoser) wrote on 2016-01-21:

#1

partial build log Edit (6.4 KiB, text/plain)

Revision history for this message

Scott Moser (smoser) wrote on 2016-01-21:

#2

For full disclosure, this is in a "cross" build environment (qemu-static).
this works for other versions of ubuntu and has worked for xenial in the past.

the error messages seem to indicate 'update-initramfs' was deferred, but the the postinst tried to copy it into place even though it wasnt there. I am able to hack around this error by just touching the file /boot/initrd.img-4.3.0-7-generic before runnign the apt-get install.

Setting up linux-image-4.3.0-7-generic (4.3.0-7.18) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
/bin/cp: cannot stat '/boot/initrd.img-4.3.0-7-generic': No such file or directory
Failed to copy /boot/initrd.img-4.3.0-7-generic to /boot/initrd.img at /var/lib/dpkg/info/linux-image-4.3.0-7-generic.postinst line 745.

Revision history for this message

Brad Figg (brad-figg) wrote on 2016-01-21: Missing required logs.

#3

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

apport-collect 1536810

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

Scott Moser (smoser) on 2016-01-22

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Andy Whitcroft (apw) wrote on 2016-01-25:

#4

@smoser -- this occurs when initramfs-tools is unable to use symlinks to reference the initrd. It then thinks it should copy the newly built one to /initrd which it cannot do because it is not yet built. This should never occur because we always use symlinks unless some configuration is lost, check /etc/kernel.conf is correctly populated in the chroot.

Revision history for this message

Scott Moser (smoser) wrote on 2016-01-25:

#5

what provides (or should create) /etc/kernel.conf ?

Revision history for this message

Scott Moser (smoser) wrote on 2016-01-25:

#6

script reproducing problem Edit (2.3 KiB, text/x-sh)

Revision history for this message

Scott Moser (smoser) wrote on 2016-01-25:

#7

I've checked, and the file exists. the content is
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
link_in_boot = yes

Revision history for this message

Scott Moser (smoser) wrote on 2016-01-25:

#8

show-kernel-img-conf Edit (1.1 KiB, text/plain)

For reference, show-kernel-img-conf.
this downloads cloud images and extracts the questioned file.
Note, there is a change in this file from wily to xenial, but the change is in place for all arch, and i'm only seeing these build failures in arm64 and armhf.

== wily armhf [wily-server-cloudimg-armhf.img]==
=== /etc/kernel-img.conf ===
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = Yes
=== /etc/cloud/build.info ===
build_name: server
serial: 20160123
== wily arm64 [wily-server-cloudimg-arm64.img]==
=== /etc/kernel-img.conf ===
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = Yes
=== /etc/cloud/build.info ===
build_name: server
serial: 20160123
== wily amd64 [wily-server-cloudimg-amd64.img]==
=== /etc/kernel-img.conf ===
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = Yes
=== /etc/cloud/build.info ===
build_name: server
serial: 20160123
== wily ppc64el [wily-server-cloudimg-ppc64el.img]==
=== /etc/kernel-img.conf ===
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = Yes
=== /etc/cloud/build.info ===
build_name: server
serial: 20160123
== xenial armhf [xenial-server-cloudimg-armhf.img]==
=== /etc/kernel-img.conf ===
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
link_in_boot = yes
=== /etc/cloud/build.info ===
build_name: server
serial: 20160125-134444
== xenial arm64 [xenial-server-cloudimg-arm64.img]==
=== /etc/kernel-img.conf ===
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
link_in_boot = yes
=== /etc/cloud/build.info ===
build_name: server
serial: 20160125-134444
== xenial amd64 [xenial-server-cloudimg-amd64.img]==
=== /etc/kernel-img.conf ===
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
=== /etc/cloud/build.info ===
build_name: server
serial: 20160125-134444
== xenial ppc64el [xenial-server-cloudimg-ppc64el.img]==
=== /etc/kernel-img.conf ===
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
link_in_boot = yes
=== /etc/cloud/build.info ===
build_name: server
serial: 20160125-134444

For reference, show-kernel-img-conf.
this downloads cloud images and extracts the questioned file.
Note, there is a change in this file from wily to xenial, but the change is in place for all arch, and i'm only seeing these build failures in arm64 and armhf.

== wily armhf  [wily-server-cloudimg-armhf.img]==
 === /etc/kernel-img.conf ===
 # Kernel Image management overrides
 # See kernel-img.conf(5) for details
 do_symlinks = Yes
 === /etc/cloud/build.info ===
 build_name: server
 serial: 20160123
== wily arm64  [wily-server-cloudimg-arm64.img]==
 === /etc/kernel-img.conf ===
 # Kernel Image management overrides
 # See kernel-img.conf(5) for details
 do_symlinks = Yes
 === /etc/cloud/build.info ===
 build_name: server
 serial: 20160123
== wily amd64  [wily-server-cloudimg-amd64.img]==
 === /etc/kernel-img.conf ===
 # Kernel Image management overrides
 # See kernel-img.conf(5) for details
 do_symlinks = Yes
 === /etc/cloud/build.info ===
 build_name: server
 serial: 20160123
== wily ppc64el  [wily-server-cloudimg-ppc64el.img]==
 === /etc/kernel-img.conf ===
 # Kernel Image management overrides
 # See kernel-img.conf(5) for details
 do_symlinks = Yes
 === /etc/cloud/build.info ===
 build_name: server
 serial: 20160123
== xenial armhf  [xenial-server-cloudimg-armhf.img]==
 === /etc/kernel-img.conf ===
 # Kernel Image management overrides
 # See kernel-img.conf(5) for details
 do_symlinks = yes
 do_bootloader = no
 link_in_boot = yes
 === /etc/cloud/build.info ===
 build_name: server
 serial: 20160125-134444
== xenial arm64  [xenial-server-cloudimg-arm64.img]==
 === /etc/kernel-img.conf ===
 # Kernel Image management overrides
 # See kernel-img.conf(5) for details
 do_symlinks = yes
 do_bootloader = no
 link_in_boot = yes
 === /etc/cloud/build.info ===
 build_name: server
 serial: 20160125-134444
== xenial amd64  [xenial-server-cloudimg-amd64.img]==
 === /etc/kernel-img.conf ===
 # Kernel Image management overrides
 # See kernel-img.conf(5) for details
 do_symlinks = yes
 do_bootloader = no
 === /etc/cloud/build.info ===
 build_name: server
 serial: 20160125-134444
== xenial ppc64el  [xenial-server-cloudimg-ppc64el.img]==
 === /etc/kernel-img.conf ===
 # Kernel Image management overrides
 # See kernel-img.conf(5) for details
 do_symlinks = yes
 do_bootloader = no
 link_in_boot = yes
 === /etc/cloud/build.info ===
 build_name: server
 serial: 20160125-134444

Revision history for this message

Scott Moser (smoser) wrote on 2016-01-25:

#9

Note, there are 2 changes fom wily to xenial in the content of that file:
a.) for arches other than amd64, we gain the 'link_in_boot = yes'
b.) there is a case change for the 'do_symlinks' setting from wily ('Yes') to xenial ('yes')

Revision history for this message

Scott Moser (smoser) wrote on 2016-01-25:

#10

It seems to be 'a' that causes the failure.
If i remove 'link_in_boot' then it works.

I've committed a change to maas-iamges to work around this at least temporarily
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/revision/268

Revision history for this message

Scott Moser (smoser) wrote on 2016-01-26:

#11

It'd be nice to track down why images have this change from wily in them, especially since it is not helpful.

Revision history for this message

Andy Whitcroft (apw) wrote on 2016-01-26:

#12

@smoser -- the header in your files implies that the kernel at least created the configuration in the first instance:

print CONF "# Kernel Image management overrides\n";
print CONF "# See kernel-img.conf(5) for details\n";

Though it only appears to write two combinations:

      if (open(CONF, ">$CONF_LOC")) {
        print CONF "# Kernel Image management overrides\n";
        print CONF "# See kernel-img.conf(5) for details\n";
        if ($loader =~ /palo/i) {
          print CONF "link_in_boot = Yes\n";
          print CONF "do_symlinks = Yes\n";
          print CONF "relative_links = Yes\n";
          print CONF "do_bootloader = No\n";
        } else {
          print CONF "do_symlinks = $do_symlink\n";
        }
        close CONF;
      }

Revision history for this message

Scott Moser (smoser) wrote on 2016-01-26:

#13

"the kernel at least created the configuration".

I don't know where the file came from, but that is the file that is in official ubuntu cloud images, built by livefs.

Revision history for this message

Scott Moser (smoser) wrote on 2016-01-28:

#14

We really need to understand what is creating this file because apparently in live build, its not the installation of a kernel.

Revision history for this message

Dan Watkins (oddbloke) wrote on 2016-01-28:

#15

It looks like this file is created by live-build/scripts/build/lb_chroot_linux-image:

cat > chroot/etc/kernel-img.conf << EOF
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
EOF

case "${LB_ARCHITECTURES}" in
alpha|amd64|hppa|i386|ia64|m68k|mips|mipsel)
;;

  *)
   cat >> chroot/etc/kernel-img.conf << EOF
link_in_boot = yes
EOF
   ;;
esac

Revision history for this message

Dimitri John Ledkov (xnox) wrote on 2016-01-28:

#16

link_in_boot is required as yes for s390x, and currently it seems like cloud-image generation is broken for s390x.

Manually, upgrading from an older cloudimage (3.3 -6- version) I had to do a small dpkg remove surgery to drop all the packages, and reinstall new metapackages.

What I found interesting, was that after "update-initramfs -u" call by kernel maintainer scripts, instead of actually generating the initramfs, it was "deffered for later by a trigger" which is not what kernel wants to do, given that it hopes to operate on the resultant files straight after (changing symlinks).

Changed in linux (Ubuntu):
importance:	Undecided → High
tags:	added: s390x

Scott Moser (smoser) on 2016-01-28

description:

updated

Revision history for this message

Dimitri John Ledkov (xnox) wrote on 2016-01-28:

#17

Hm, i don't think update-initramfs does the right thing:

linux-image-*)
        if [ -z "$INITRAMFS_TOOLS_KERNEL_HOOK" ]; then
                # kernel maintainer script called us directly; ignore
                # it and let the hook script handle it instead
                echo "update-initramfs: deferring update (hook will be called later)"
                exit 0
        fi
        ;;

it seems like a special variable needs to be set, to actually make initramfs create things.

Revision history for this message

Dimitri John Ledkov (xnox) wrote on 2016-01-28:

#18

Unpacking linux-generic (4.3.0.7.8) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up linux-image-4.3.0-7-generic (4.3.0-7.18) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
/bin/cp: cannot stat '/boot/initrd.img-4.3.0-7-generic': No such file or directory
Failed to copy /boot/initrd.img-4.3.0-7-generic to /boot/initrd.img at /var/lib/dpkg/info/linux-image-4.3.0-7-generic.postinst line 745.

Implies that, update-initramfs was called, yet it decided to defer.
No initrds created.
None possible to copy.
Boom.

Revision history for this message

Dimitri John Ledkov (xnox) wrote on 2016-01-31:

#19

linux-postinst.patch Edit (694 bytes, text/plain)

Revision history for this message

Dimitri John Ledkov (xnox) wrote on 2016-01-31:

#20

Download full text (3.6 KiB)

Looking at the postinst script, it calls update-initramfs -u and expects it to do somethin, i.e. create the initramfs.

However, it can choose to not do so, and deffer the update. And thus not create an initramfs. However, when we are upgrading to a new kernel image, we expect to generate an initramfs cause we will be fixing symlinks and so on right after.

I have linux-image-4.3.0-6.17 installed, via linux-virtual metapackage on an old cloud image (see my private fileshare). And upgrading that to xenial/release 4.3.0-7.18 fails like so:

ubuntu@ubuntu:~$ dpkg -l | grep linux
ii console-setup-linux 1.108ubuntu10 all Linux specific part of console-setup
ii libselinux1:s390x 2.4-3 s390x SELinux runtime shared libraries
ii linux-headers-4.3.0-6 4.3.0-6.17 all Header files related to Linux kernel version 4.3.0
ii linux-headers-4.3.0-6-generic 4.3.0-6.17 s390x Linux kernel headers for version 4.3.0 on System 390x SMP
ii linux-headers-generic 4.3.0.6.7 s390x Generic Linux kernel headers
ii linux-headers-virtual 4.3.0.6.7 s390x Transitional package.
ii linux-image-4.3.0-6-generic 4.3.0-6.17 s390x Linux kernel image for version 4.3.0 on System 390x SMP
ii linux-image-virtual 4.3.0.6.7 s390x This package will always depend on the latest minimal generic kernel image.
ii linux-virtual 4.3.0.6.7 s390x Minimal Generic Linux kernel and headers
ii util-linux 2.27.1-1ubuntu3 s390x Miscellaneous system utilities
ubuntu@ubuntu:~$

# upgrading to release (to 4.3.0-7.18)

...

Setting up linux-image-4.3.0-7-generic (4.3.0-7.18) ...
Progress: [ 76%] [#############################################.............]
update-initramfs: deferring update (hook will be called later)
cp: cannot stat ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory
Failed to copy /boot/initrd.img-4.3.0-7-generic to /boot/initrd.img at /var/lib/dpkg/info/linux-imageProgress: [ 77%] [#############################################.............]
dpkg: error processing package linux-image-4.3.0-7-generic (--configure):
subprocess installed post-installation script returned error exit status 1

...

dpkg: dependency problems prevent configuration of linux-image-virtual:
linux-image-virtual depends on linux-image-4.3.0-7-generic; however:
Package linux-image-4.3.0-7-generic is not configured yet.

dpkg: error processing package linux-image-virtual (--configure):
dependency problems - leaving unconfigured
Setting up linux-headers-generic (4.3.0.7.8) ...No apport report written because the error message indicates its a followup error from a previous failure.

Setting up linux-headers-virtual (4.3.0.7.8) ...
dpkg: dependency problems prevent configuration of linux-virtual:
linux-virtual depends ...

This bug was fixed in the package linux - 4.4.0-4.19

---------------
linux (4.4.0-4.19) xenial; urgency=low

* update ZFS and SPL to 0.6.5.4 (LP: #1542296)
    - [Config] update spl/zfs version
    - SAUCE: (noup) Update spl to 0.6.5.4-0ubuntu2, zfs to 0.6.5.4-0ubuntu1
    - [Config] reconstruct -- drop links for zfs userspace components
    - [Config] reconstruct -- drop links for zfs userspace components -- restore spec links

* recvmsg() fails SCM_CREDENTIALS request with EOPNOTSUPP. (LP: #1540731)
    - Revert "af_unix: Revert 'lock_interruptible' in stream receive code"

* lxc: ADT exercise test failing with linux-4.4.0-3.17  (LP: #1542049)
    - Revert "UBUNTU: SAUCE: apparmor: fix sleep from invalid context"

* WARNING: at /build/linux-lts-wily-W0lTWH/linux-lts-wily-4.2.0/net/core/skbuff.c:4174 (Travis IB) (LP: #1541326)
    - SAUCE: IB/IPoIB: Do not set skb truesize since using one linearskb

* backport Microsoft Precision Touchpad palm rejection patch (LP: #1541671)
    - HID: multitouch: enable palm rejection if device implements confidence usage

* [Ubuntu 16.04] Update qla2xxx driver for POWER (QLogic) (LP: #1541456)
    - qla2xxx: Remove unavailable firmware files
    - qla2xxx: Enable Extended Logins support
    - qla2xxx: Enable Exchange offload support.
    - qla2xxx: Enable Target counters in DebugFS.
    - qla2xxx: Add FW resource count in DebugFS.
    - qla2xxx: Added interface to send explicit LOGO.
    - qla2xxx: Delete session if initiator is gone from FW
    - qla2xxx: Wait for all conflicts before ack'ing PLOGI
    - qla2xxx: Replace QLA_TGT_STATE_ABORTED with a bit.
    - qla2xxx: Remove dependency on hardware_lock to reduce lock contention.
    - qla2xxx: Add irq affinity notification
    - qla2xxx: Add selective command queuing
    - qla2xxx: Move atioq to a different lock to reduce lock contention
    - qla2xxx: Disable ZIO at start time.
    - qla2xxx: Set all queues to 4k
    - qla2xxx: Check for online flag instead of active reset when transmitting responses
    - scsi: qla2xxxx: avoid type mismatch in comparison

* [Hyper-V] PCI Passthrough (LP: #1541120)
    - x86/irq: Export functions to allow MSI domains in modules
    - genirq/msi: Export functions to allow MSI domains in modules

* Update lpfc driver to 11.0.0.10 (LP: #1541592)
    - lpfc: Fix FCF Infinite loop in lpfc_sli4_fcf_rr_next_index_get.
    - lpfc: Fix the FLOGI discovery logic to comply with T11 standards
    - lpfc: Fix RegLogin failed error seen on Lancer FC during port bounce
    - lpfc: Fix driver crash when module parameter lpfc_fcp_io_channel set to 16
    - lpfc: Fix crash in fcp command completion path.
    - lpfc: Modularize and cleanup FDMI code in driver
    - lpfc: Fix RDP Speed reporting.
    - lpfc: Fix RDP ACC being too long.
    - lpfc: Make write check error processing more resilient
    - lpfc: Use new FDMI speed definitions for 10G, 25G and 40G FCoE.
    - lpfc: Fix mbox reuse in PLOGI completion
    - lpfc: Fix external loopback failure.
    - lpfc: Add logging for misconfigured optics.
    - lpfc: Delete unnecessary checks before the function call "mempool_destroy"
    - lpfc: Use kzalloc instead of kmalloc
    - lpfc: Update version to 11.0.0.10 for upstream patch set

* Miscellaneous Ubuntu changes
    - [Config] CONFIG_ARM64_VA_BITS=48
    - [Config] Fixed Vcs-Git

* Miscellaneous upstream changes
    - cxl: Fix possible idr warning when contexts are released
    - cxl: use correct operator when writing pcie config space values
    - cxlflash: drop unlikely before IS_ERR_OR_NULL
    - cxl: Fix DSI misses when the context owning task exits
    - cxlflash: Removed driver date print
    - cxlflash: Fix to resolve cmd leak after host reset
    - cxlflash: Resolve oops in wait_port_offline
    - cxlflash: Enable device id for future IBM CXL adapter
    - cxl: fix build for GCC 4.6.x
    - cxl: use -Werror only with CONFIG_PPC_WERROR
    - cxl: Enable PCI device ID for future IBM CXL adapter

-- Andy Whitcroft <apw@canonical.com>  Fri, 05 Feb 2016 14:58:51 +0000

Changed in linux (Ubuntu):
status:	Fix Committed → Fix Released

Revision history for this message

Scott Moser (smoser) wrote on 2016-02-17:

#25

This really never got fixed to my knowledge.
https://pastebin.canonical.com/150018/ shows the general failure occuring on arm64.

Changed in linux (Ubuntu):
status:	Fix Released → Confirmed

Andy Whitcroft (apw) on 2016-02-17

Changed in linux (Ubuntu):
status:	Confirmed → In Progress
assignee:	nobody → Andy Whitcroft (apw)

Revision history for this message

Scott Moser (smoser) wrote on 2016-02-17:

#26

Reproduce for this issue is as simple as downloading -root.tar.xz (or -root.tar.gz) from http://cloud-images.ubuntu.com/daily/server/xenial , then extracting it, chrooting and apt-get installing a kernel.

I believe that amd64 works fine, so to see failure you have to either use qemu-user-static or actually run on the correct arch.

# if running non-native arch, use qemu-user-static
sudo apt-get install -qy qemu-user-static
wget http://cloud-images.ubuntu.com/daily/server/xenial/current/xenial-server-cloudimg-arm64-root.tar.xz

exdir=$(mktemp -d)
mkdir "$exdir"
sudo tar -C "$exdir" -xSpf xenial-server-cloudimg-arm64-root.tar.xz

# fix resolv.conf for dns to your local system's settings
sudo mv "$exdir/etc/resolv.conf" "${exdir}/etc/resolv.conf.dist"
sudo cp /etc/resolv.conf "$exdir/etc/resolv.conf"

# if cross, patch in qemu-user-static
sudo cp /usr/bin/qemu-aarch64-static "$exdir/usr/bin/"
sudo chroot "$exdir" sh -exc 'apt-get update && apt-get install -qy linux-generic'
...
Unpacking linux-generic (4.4.0.4.3) ...
Setting up linux-image-4.4.0-4-generic (4.4.0-4.19) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
/bin/cp: cannot stat ‘/boot/initrd.img-4.4.0-4-generic’: No such file or directory
Failed to copy /boot/initrd.img-4.4.0-4-generic to /boot/initrd.img at /var/lib/dpkg/info/linux-image-4.4.0-4-generic.postinst line 745.
dpkg: error processing package linux-image-4.4.0-4-generic (--configure):
subprocess installed post-installation script returned error exit status 2

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-02-26:

#27

Download full text (10.1 KiB)

This bug was fixed in the package linux - 4.4.0-8.23

---------------
linux (4.4.0-8.23) xenial; urgency=low

* cgroup namespace mounts broken in containers (LP: #1549398)
- SAUCE: kernfs: Always set super block owner to init_user_ns

  * 4.4.0-7.22 no longer boots on arm64 (LP: #1547718)
    - arm64: mm: avoid calling apply_to_page_range on empty range
    - UBUNTU SAUCE: arm: mm: avoid calling apply_to_page_range on empty range

* kernel install failed /bin/cp: cannot stat ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory (LP: #1536810)
- [Config] postinst -- handle recreating symlinks when a real file is present

  * insecure overlayfs xattrs handling in copy_up (LP: #1534961)
    - SAUCE: cred: Add clone_cred() interface
    - SAUCE: overlayfs: Use mounter's credentials instead of selectively raising caps
    - SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs
    - SAUCE: overlayfs: Be more careful about copying up sxid files
    - SAUCE: overlayfs: Propogate nosuid from lower and upper mounts

  * overlayfs over fuse should refuse copy_up of files if uid/gid not mapped (LP: #1535150)
    - SAUCE: cred: Add clone_cred() interface
    - SAUCE: overlayfs: Use mounter's credentials instead of selectively raising caps
    - SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs
    - SAUCE: overlayfs: Be more careful about copying up sxid files
    - SAUCE: overlayfs: Propogate nosuid from lower and upper mounts

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace (LP: #1531747)
    - SAUCE: cred: Add clone_cred() interface
    - SAUCE: overlayfs: Use mounter's credentials instead of selectively raising caps
    - SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Update Intel ethernet drivers to Fortville SW5 (LP: #1547674)
    - net: bulk free infrastructure for NAPI context, use napi_consume_skb
    - net: Add eth_platform_get_mac_address() helper.
    - i40e: Add mac_filter_element at the end of the list instead of HEAD
    - i40e/i40evf: Fix RSS rx-flow-hash configuration through ethtool
    - i40e: Replace X722 mac check in ethtool get_settings
    - i40evf: allow channel bonding of VFs
    - i40e: define function capabilities in only one place
    - i40evf: null out ring pointers on free
    - i40e: Cleanup the code with respect to restarting autoneg
    - i40e: update features with right offload
    - i40e: bump version to 1.4.10
    - i40e: add new device IDs for X722
    - i40e: Extend ethtool RSS hooks for X722
    - i40e/i40evf: Fix for UDP/TCP RSS for X722
    - i40evf: add new write-back mode
    - i40e/i40evf: Use private workqueue
    - i40e: add new proxy-wol bit for X722
    - i40e: Limit DCB FW version checks to X710/XL710 devices
    - i40e: AQ Add Run PHY Activity struct
    - i40e: AQ Geneve cloud tunnel type
    - i40e: AQ Add external power class to get link status
    - i40e: add 100Mb ethtool reporting
    - ixgbe: bulk free SKBs during TX completion cleanup cycle
    - igb: Remove unnecessary flag setting in igb_set_flag_queue_pairs()
    - igb: Unpair the queues when changing the number of queues...

This bug was fixed in the package linux - 4.4.0-8.23

---------------
linux (4.4.0-8.23) xenial; urgency=low

* cgroup namespace mounts broken in containers (LP: #1549398)
    - SAUCE: kernfs: Always set super block owner to init_user_ns

* 4.4.0-7.22 no longer boots on arm64 (LP: #1547718)
    - arm64: mm: avoid calling apply_to_page_range on empty range
    - UBUNTU SAUCE: arm: mm: avoid calling apply_to_page_range on empty range

* kernel install failed /bin/cp: cannot stat ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory (LP: #1536810)
    - [Config] postinst -- handle recreating symlinks when a real file is present

* insecure overlayfs xattrs handling in copy_up (LP: #1534961)
    - SAUCE: cred: Add clone_cred() interface
    - SAUCE: overlayfs: Use mounter's credentials instead of selectively raising caps
    - SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs
    - SAUCE: overlayfs: Be more careful about copying up sxid files
    - SAUCE: overlayfs: Propogate nosuid from lower and upper mounts

* overlayfs over fuse should refuse copy_up of files if uid/gid not mapped (LP: #1535150)
    - SAUCE: cred: Add clone_cred() interface
    - SAUCE: overlayfs: Use mounter's credentials instead of selectively raising caps
    - SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs
    - SAUCE: overlayfs: Be more careful about copying up sxid files
    - SAUCE: overlayfs: Propogate nosuid from lower and upper mounts

* overlay: mkdir fails if directory exists in lowerdir in a user namespace (LP: #1531747)
    - SAUCE: cred: Add clone_cred() interface
    - SAUCE: overlayfs: Use mounter's credentials instead of selectively raising caps
    - SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

* Update Intel ethernet drivers to Fortville SW5 (LP: #1547674)
    - net: bulk free infrastructure for NAPI context, use napi_consume_skb
    - net: Add eth_platform_get_mac_address() helper.
    - i40e: Add mac_filter_element at the end of the list instead of HEAD
    - i40e/i40evf: Fix RSS rx-flow-hash configuration through ethtool
    - i40e: Replace X722 mac check in ethtool get_settings
    - i40evf: allow channel bonding of VFs
    - i40e: define function capabilities in only one place
    - i40evf: null out ring pointers on free
    - i40e: Cleanup the code with respect to restarting autoneg
    - i40e: update features with right offload
    - i40e: bump version to 1.4.10
    - i40e: add new device IDs for X722
    - i40e: Extend ethtool RSS hooks for X722
    - i40e/i40evf: Fix for UDP/TCP RSS for X722
    - i40evf: add new write-back mode
    - i40e/i40evf: Use private workqueue
    - i40e: add new proxy-wol bit for X722
    - i40e: Limit DCB FW version checks to X710/XL710 devices
    - i40e: AQ Add Run PHY Activity struct
    - i40e: AQ Geneve cloud tunnel type
    - i40e: AQ Add external power class to get link status
    - i40e: add 100Mb ethtool reporting
    - ixgbe: bulk free SKBs during TX completion cleanup cycle
    - igb: Remove unnecessary flag setting in igb_set_flag_queue_pairs()
    - igb: Unpair the queues when changing the number of queues
    - igb/igbvf: don't give up
    - igb: clean up code for setting MAC address
    - igb: Refactor VFTA configuration
    - igb: Allow asymmetric configuration of MTU versus Rx frame size
    - igb: Do not factor VLANs into RLPML calculation
    - igb: Always enable VLAN 0 even if 8021q is not loaded
    - igb: Merge VLVF configuration into igb_vfta_set
    - igb: Clean-up configuration of VF port VLANs
    - igb: Add support for VLAN promiscuous with SR-IOV and NTUPLE
    - igb: Drop unnecessary checks in transmit path
    - igb: Enable use of "bridge fdb add" to set unicast table entries
    - igb: Add workaround for VLAN tag stripping on 82576
    - i40e: AQ Shared resource flags
    - i40e: AQ Add set_switch_config
    - i40e: AQ Add VXLAN-GPE tunnel type
    - i40e: AQ thermal sensor control struct
    - i40e: Bump AQ minor version to 1.5 for new FW features
    - i40e: Store lan_vsi_idx and lan_vsi_id in the right size
    - i40e: fix write-back-on-itr to work with legacy itr
    - i40e: add counter for arq overflows
    - i40e: add 20G speed for Tx bandwidth calculations
    - i40e: refactor DCB function
    - i40e: add a little more to an NVM update debug message
    - i40evf: enable bus master after reset
    - i40e: add netdev info to VSI dump
    - i40e: remove VF device IDs from PF
    - i40e: trivial: remove unnecessary local var
    - i40e/i40evf: Bump i40e to 1.4.11 and i40evf to 1.4.7
    - net: ixgbe: add minimal parser details for ixgbe
    - i40e: trivial: drop duplicate definition
    - i40e: trivial: fix missing space
    - i40e: fix bug in dma sync
    - i40e: do TSO only if CHECKSUM_PARTIAL is set
    - i40e: allocate memory safer
    - i40e: fix: do not sleep in netdev_ops
    - i40e: APIs to Add/remove port mirroring rules
    - i40e: negate PHY int mask bits
    - i40e: drop unused function
    - i40e: count allocation errors
    - i40e: avoid large memcpy by assigning struct
    - i40e/i40evf: bump version to 1.4.12/1.4.8
    - i40e: Enable Geneve offload for FW API ver > 1.4 for XL710/X710 devices
    - i40e: add priv flag for automatic rule eviction
    - i40e: use eth_platform_get_mac_address()
    - i40e: move sync_vsi_filters up in service_task
    - i40e: Make the DCB firmware checks for X710/XL710 only
    - i40e: set shared bit for multicast filters
    - i40e: add VEB stat control and remove L2 cloud filter
    - i40e: use new add_veb calling with VEB stats control
    - i40e: Refactor force_wb and WB_ON_ITR functionality code
    - i40evf: Change vf driver string to reflect all products i40evf supports
    - i40e/i40evf: don't lose interrupts
    - i40e/i40evf: try again after failure
    - i40e: dump descriptor indexes in hex
    - i40e/i40evf: use __GFP_NOWARN
    - i40e/i40evf: use pages correctly in Rx
    - i40e/i40evf: use logical operators, not bitwise
    - i40e: properly show packet split status in debugfs
    - i40e/i40evf: Bump version
    - ixgbe: use u32 instead of __u32 in model header
    - ixgbe: fix dates on header of ixgbe_model.h
    - i40e: get rid of magic number
    - i40e: drop unused debugfs file "dump"
    - i40evf: support packet split receive
    - i40e: trivial: cleanup use of pf->hw
    - i40e: Add a SW workaround for lost interrupts
    - i40e: Fix PROMISC mode for Multi-function per port (MFP) devices
    - i40e: Removal of code which relies on BASE VEB SEID
    - i40e/i40evf: avoid atomics
    - i40e: Do not disable queues in the Legacy/MSI Interrupt handler
    - i40e: expand comment
    - i40e: better error reporting for nvmupdate
    - i40evf: set adapter state on reset failure
    - i40e: clean event descriptor before use
    - i40e: When in promisc mode apply promisc mode to Tx Traffic as well
    - i40e/i40evf: Bump i40e to 1.4.15 and i40evf to 1.4.11.
    - i40e/i40evf: Drop outer checksum offload that was not requested
    - i40e/i40evf: Use u64 values instead of casting them in TSO function
    - i40e/i40evf: Factor out L4 header and checksum from L3 bits in TSO path
    - i40e/i40evf: Consolidate all header changes into TSO function
    - i40e/i40evf: Replace header pointers with unions of pointers in Tx checksum path
    - i40e/i40evf: Add support for IPv4 encapsulated in IPv6
    - i40e/i40evf: Handle IPv6 extension headers in checksum offload
    - i40e/i40evf: Do not write to descriptor unless we complete
    - i40e/i40evf: Add exception handling for Tx checksum
    - i40e/i40evf: Clean-up Rx packet checksum handling
    - i40e/i40evf: Enable support for SKB_GSO_UDP_TUNNEL_CSUM
    - i40e: Fix ATR in relation to tunnels
    - i40e: Do not drop support for IPv6 VXLAN or GENEVE tunnels
    - i40e: Update feature flags to reflect newly enabled features
    - i40evf: Update feature flags to reflect newly enabled features
    - i40e: Add support for ATR w/ IPv6 extension headers
    - i40e/i40evf: Break up xmit_descriptor_count from maybe_stop_tx
    - i40e/i40evf: Rewrite logic for 8 descriptor per packet check
    - i40e/i40evf: Move Tx checksum closer to TSO
    - i40e: Add functions to blink led on 10GBaseT PHY
    - i40e: Fix led blink capability for 10GBaseT PHY
    - i40e: Increase timeout when checking GLGEN_RSTAT_DEVSTATE bit
    - i40e: Do not wait for Rx queue disable in DCB reconfig
    - i40e: Fix for unexpected messaging
    - i40e: Expose some registers to program parser, FD and RSS logic
    - i40e: add check for null VSI
    - i40e: add adminq commands for Rx CTL registers
    - i40e: implement and use Rx CTL helper functions
    - i40e: Use the new rx ctl register helpers. Don't use AQ calls from clear_hw.
    - i40e: suspend scheduling during driver unload
    - i40e: let go of the past
    - i40e/i40evf: Bump i40e to 1.4.25 and i40evf to 1.4.15

* MPT3SAS Driver update for next kernel release (LP: #1512221)
    - mpt3sas: A correction in unmap_resources
    - mpt3sas: Added support for high port count HBA variants.
    - mpt3sas: Used IEEE SGL instead of MPI SGL while framing a SMP Passthrough request message.
    - mpt3sas: Fix static analyzer(coverity) tool identified defects
    - mpt3sas: Never block the Enclosure device
    - mpt3sas: Make use of additional HighPriority credit message frames for sending SCSI IO's
    - mpt3sas: Added smp_affinity_enable module parameter.
    - mpt3sas: Add support for configurable Chain Frame Size
    - mpt3sas: Updated MPI Header to 2.00.42
    - mpt3sas: Fix for Asynchronous completion of timedout IO and task abort of timedout IO.
    - mpt3sas: Updating mpt3sas driver version to 12.100.00.00
    - mpt3sas: Remove cpumask_clear for zalloc_cpumask_var and don't free free_cpu_mask_var before reply_q

* /sys/class/scsi_host/hostN/partition_number and .../mad_version showing up BE on LE Ubuntu. (ibmvscsi) (LP: #1547153)
    - ibmvscsi: Add endian conversions to sysfs attribute show functions

* Miscellaneous Ubuntu changes
    - [Packaging] git-ubuntu-log -- output should be utf-8
    - [Packaging] git-ubuntu-log -- handle invalid or private bugs

-- Andy Whitcroft <apw@canonical.com>  Wed, 24 Feb 2016 20:34:49 +0000

Changed in linux (Ubuntu):
status:	In Progress → Fix Released

Revision history for this message

Scott Moser (smoser) wrote on 2016-03-01:

#28

Verified fixed in arm64 image for 20160227.
I noticed it does still have the bogus 'initrd.img file:
$ ls -l $exdir/boot
total 20592
drwxr-xr-x 2 root root 4096 Feb 27 14:36 grub
-rw-r--r-- 1 root root 21079648 Feb 27 14:38 initrd.img

But the initrd.img file does not seem to cause a problem here, and after install we have a symlink to the proper place.
$ ls -l $exdir/boot/initrd.img
lrwxrwxrwx 1 root root 26 Mar 1 15:13 /tmp/tmp.RGUZJZwhWr/boot/initrd.img -> initrd.img-4.4.0-8-generic

I've reverted my workaround change in maas-images at revno 284.

Ubuntu
linux package

kernel install failed /bin/cp: cannot stat ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory

Bug Description

Duplicates of this bug

Other bug subscribers

Patches

Bug attachments

Remote bug watches

Changed in linux (Ubuntu):
status:	Confirmed → Fix Committed

Ubuntulinux package

kernel install failed /bin/cp: cannot stat ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory

Bug Description

Duplicates of this bug

Other bug subscribers

Patches

Bug attachments

Remote bug watches

Ubuntu
linux package