[Kernel-packages] [Bug 1666897] Re: snaps with classic + jailmode confinement started to fail on zesty
This bug was fixed in the package linux - 4.8.0-44.47 --- linux (4.8.0-44.47) yakkety; urgency=low * linux: 4.8.0-44.47 -proposed tracker (LP: #1674986) * snaps with classic + jailmode confinement started to fail on zesty (LP: #1666897) - Revert "UBUNTU: SAUCE: apparmor: fix link auditing failure due to, uninitialized var" - Revert "UBUNTU: SAUCE: fix regression with domain change in complain mode" - Revert "UBUNTU: SAUCE: apparmor: flock mediation is not being enforced on cache check" - Revert "UBUNTU: SAUCE: apparmor: null profiles should inherit parent control flags" - Revert "UBUNTU: SAUCE: apparmor: fix ns ref count link when removing profiles from policy" - Revert "UBUNTU: SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using stacked namespaces" - Revert "UBUNTU: SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails" - Revert "UBUNTU: SAUCE: apparmor: Don't audit denied access of special apparmor .null file" - Revert "UBUNTU: SAUCE: apparmor: fix label leak when new label is unused" - Revert "UBUNTU: SAUCE: apparmor: fix reference count bug in label_merge_insert()" - Revert "UBUNTU: SAUCE: apparmor: fix replacement race in reading rawdata" - Revert "UBUNTU: SAUCE: apparmor: fix cross ns perm of unix domain sockets" linux (4.8.0-42.45) yakkety; urgency=low * linux: 4.8.0-42.45 -proposed tracker (LP: #1671176) * Regression in 4.4.0-65-generic causes very frequent system crashes (LP: #1669611) - Revert "UBUNTU: SAUCE: apparmor: fix lock ordering for mkdir" - Revert "UBUNTU: SAUCE: apparmor: fix leak on securityfs pin count" - Revert "UBUNTU: SAUCE: apparmor: fix reference count leak when securityfs_setup_d_inode() fails" - Revert "UBUNTU: SAUCE: apparmor: fix not handling error case when securityfs_pin_fs() fails" * NFS client : permission denied when trying to access subshare, since kernel 4.4.0-31 (LP: #1649292) - fs: Better permission checking for submounts * shaking screen (LP: #1651981) - drm/radeon: drop verde dpm quirks * [0bda:0328] Card reader failed after S3 (LP: #1664809) - usb: hub: Wait for connection to be reestablished after port reset * linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial 4.4.0-63.84~14.04.2 (LP: #1664912) - SAUCE: apparmor: fix link auditing failure due to, uninitialized var * In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2) (LP: #1656908) - SAUCE: ima: Downgrade error to warning * 16.04.2: Extra patches for POWER9 (LP: #1664564) - powerpc/mm: Fix no execute fault handling on pre-POWER5 - powerpc/mm: Fix spurrious segfaults on radix with autonuma * ibmvscsis: Add SGL LIMIT (LP: #1662551) - ibmvscsis: Add SGL limit * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions) (LP: #1663687) - scsi: storvsc: Enable tracking of queue depth - scsi: storvsc: Remove the restriction on max segment size - scsi: storvsc: Enable multi-queue support - scsi: storvsc: use tagged SRB requests if supported by the device - scsi: storvsc: properly handle SRB_ERROR when sense message is present - scsi: storvsc: properly set residual data length on errors * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs caused KVM host hung and all KVM guests down. (LP: #1651248) - KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT - KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter - KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends - KVM: PPC: Book 3S: XICS: Implement ICS P/Q states - KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend * ISST-LTE:pNV: ppc64_cpu command is hung w HDs, SSDs and NVMe (LP: #1662666) - blk-mq: Avoid memory reclaim when remapping queues - blk-mq: Fix failed allocation path when mapping queues - blk-mq: Always schedule hctx->next_cpu * systemd-udevd hung in blk_mq_freeze_queue_wait testing unpartitioned NVMe drive (LP: #1662673) - percpu-refcount: fix reference leak during percpu-atomic transition * [Yakkety SRU] Enable KEXEC support in ARM64 kernel (LP: #1662554) - [Config] Enable KEXEC support in ARM64. * [Hyper-V] Fix ring buffer handling to avoid host throttling (LP: #1661430) - Drivers: hv: vmbus: On write cleanup the logic to interrupt the host - Drivers: hv: vmbus: On the read path cleanup the logic to interrupt the host - Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read() * brd module compiled as built-in (LP: #1593293) - CONFIG_BLK_DEV_RAM=m * regession tests failing after stackprofile test is run (LP: #1661030) - SAUCE: fix regression with domain change in complain mode * Permission denied and inconsistent behavior
[Kernel-packages] [Bug 1666897] Re: snaps with classic + jailmode confinement started to fail on zesty
This bug was fixed in the package linux - 4.4.0-70.91 --- linux (4.4.0-70.91) xenial; urgency=low * linux: 4.4.0-70.91 -proposed tracker (LP: #1674938) * snaps with classic + jailmode confinement started to fail on zesty (LP: #1666897) - Revert "UBUNTU: SAUCE: apparmor: fix link auditing failure due to, uninitialized var" - Revert "UBUNTU: SAUCE: fix regression with domain change in complain mode" - Revert "UBUNTU: SAUCE: apparmor: flock mediation is not being enforced on cache check" - Revert "UBUNTU: SAUCE: apparmor: null profiles should inherit parent control flags" - Revert "UBUNTU: SAUCE: apparmor: fix ns ref count link when removing profiles from policy" - Revert "UBUNTU: SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using stacked namespaces" - Revert "UBUNTU: SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails" - Revert "UBUNTU: SAUCE: apparmor: Don't audit denied access of special apparmor .null file" - Revert "UBUNTU: SAUCE: apparmor: fix label leak when new label is unused" - Revert "UBUNTU: SAUCE: apparmor: fix reference count bug in label_merge_insert()" - Revert "UBUNTU: SAUCE: apparmor: fix replacement race in reading rawdata" - Revert "UBUNTU: SAUCE: apparmor: fix cross ns perm of unix domain sockets" -- Stefan BaderWed, 22 Mar 2017 09:28:43 +0100 ** Changed in: linux (Ubuntu Yakkety) Status: New => Fix Released -- 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/1666897 Title: snaps with classic + jailmode confinement started to fail on zesty Status in snapd: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: We just noticed that zesty stated to fail when a snap using classic confinement is installed in jailmode. $ snap install --jailmode --classic python0 $ python0 (doesn't work) /snap/python0/2/usr/bin/python0: error while loading shared libraries: libm.so.6: failed to map segment from shared object And in the system log you can see: [ 2929.841318] audit: type=1400 audit(1487770576.927:40): apparmor="DENIED" operation="file_mmap" profile="snap.python0.python0" name="/snap/core/1264/lib/x86_64-linux-gnu/libm-2.23.so" pid=5235 comm="python0" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1666897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666897] Re: snaps with classic + jailmode confinement started to fail on zesty
This bug was fixed in the package linux - 4.4.0-70.91 --- linux (4.4.0-70.91) xenial; urgency=low * linux: 4.4.0-70.91 -proposed tracker (LP: #1674938) * snaps with classic + jailmode confinement started to fail on zesty (LP: #1666897) - Revert "UBUNTU: SAUCE: apparmor: fix link auditing failure due to, uninitialized var" - Revert "UBUNTU: SAUCE: fix regression with domain change in complain mode" - Revert "UBUNTU: SAUCE: apparmor: flock mediation is not being enforced on cache check" - Revert "UBUNTU: SAUCE: apparmor: null profiles should inherit parent control flags" - Revert "UBUNTU: SAUCE: apparmor: fix ns ref count link when removing profiles from policy" - Revert "UBUNTU: SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using stacked namespaces" - Revert "UBUNTU: SAUCE: apparmor: fix oops in bind_mnt when dev_path lookup fails" - Revert "UBUNTU: SAUCE: apparmor: Don't audit denied access of special apparmor .null file" - Revert "UBUNTU: SAUCE: apparmor: fix label leak when new label is unused" - Revert "UBUNTU: SAUCE: apparmor: fix reference count bug in label_merge_insert()" - Revert "UBUNTU: SAUCE: apparmor: fix replacement race in reading rawdata" - Revert "UBUNTU: SAUCE: apparmor: fix cross ns perm of unix domain sockets" -- Stefan BaderWed, 22 Mar 2017 09:28:43 +0100 ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Released -- 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/1666897 Title: snaps with classic + jailmode confinement started to fail on zesty Status in snapd: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: We just noticed that zesty stated to fail when a snap using classic confinement is installed in jailmode. $ snap install --jailmode --classic python0 $ python0 (doesn't work) /snap/python0/2/usr/bin/python0: error while loading shared libraries: libm.so.6: failed to map segment from shared object And in the system log you can see: [ 2929.841318] audit: type=1400 audit(1487770576.927:40): apparmor="DENIED" operation="file_mmap" profile="snap.python0.python0" name="/snap/core/1264/lib/x86_64-linux-gnu/libm-2.23.so" pid=5235 comm="python0" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1666897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666897] Re: snaps with classic + jailmode confinement started to fail on zesty
** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1666897 Title: snaps with classic + jailmode confinement started to fail on zesty Status in snapd: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux source package in Yakkety: New Bug description: We just noticed that zesty stated to fail when a snap using classic confinement is installed in jailmode. $ snap install --jailmode --classic python0 $ python0 (doesn't work) /snap/python0/2/usr/bin/python0: error while loading shared libraries: libm.so.6: failed to map segment from shared object And in the system log you can see: [ 2929.841318] audit: type=1400 audit(1487770576.927:40): apparmor="DENIED" operation="file_mmap" profile="snap.python0.python0" name="/snap/core/1264/lib/x86_64-linux-gnu/libm-2.23.so" pid=5235 comm="python0" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1666897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666897] Re: snaps with classic + jailmode confinement started to fail on zesty
@Denis -- your issue was caused by an attempt to back out the snapd update to 2.23.1 in the archive without also backing out the linux updates that depended on it. These have now been rolled back also pending a fix for the underlying issue (a dpkg bug trigging upgrade failures). -- 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/1666897 Title: snaps with classic + jailmode confinement started to fail on zesty Status in snapd: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: We just noticed that zesty stated to fail when a snap using classic confinement is installed in jailmode. $ snap install --jailmode --classic python0 $ python0 (doesn't work) /snap/python0/2/usr/bin/python0: error while loading shared libraries: libm.so.6: failed to map segment from shared object And in the system log you can see: [ 2929.841318] audit: type=1400 audit(1487770576.927:40): apparmor="DENIED" operation="file_mmap" profile="snap.python0.python0" name="/snap/core/1264/lib/x86_64-linux-gnu/libm-2.23.so" pid=5235 comm="python0" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1666897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666897] Re: snaps with classic + jailmode confinement started to fail on zesty
This fix breaks Ubuntu 16.04: update-manager did a partial update. It elected to keep snapd (2.22.6) and remove linux-generic and linux-image- generic. This plus a kernel update (4.4.0.67), I ended up with kernel 4.4.0.67 without linux-image-extras of the same version. After reboot, no network, no sound, and so on. -- 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/1666897 Title: snaps with classic + jailmode confinement started to fail on zesty Status in snapd: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: We just noticed that zesty stated to fail when a snap using classic confinement is installed in jailmode. $ snap install --jailmode --classic python0 $ python0 (doesn't work) /snap/python0/2/usr/bin/python0: error while loading shared libraries: libm.so.6: failed to map segment from shared object And in the system log you can see: [ 2929.841318] audit: type=1400 audit(1487770576.927:40): apparmor="DENIED" operation="file_mmap" profile="snap.python0.python0" name="/snap/core/1264/lib/x86_64-linux-gnu/libm-2.23.so" pid=5235 comm="python0" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1666897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666897] Re: snaps with classic + jailmode confinement started to fail on zesty
** Package changed: linux-meta (Ubuntu) => linux (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/1666897 Title: snaps with classic + jailmode confinement started to fail on zesty Status in snapd: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: We just noticed that zesty stated to fail when a snap using classic confinement is installed in jailmode. $ snap install --jailmode --classic python0 $ python0 (doesn't work) /snap/python0/2/usr/bin/python0: error while loading shared libraries: libm.so.6: failed to map segment from shared object And in the system log you can see: [ 2929.841318] audit: type=1400 audit(1487770576.927:40): apparmor="DENIED" operation="file_mmap" profile="snap.python0.python0" name="/snap/core/1264/lib/x86_64-linux-gnu/libm-2.23.so" pid=5235 comm="python0" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1666897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666897] Re: snaps with classic + jailmode confinement started to fail on zesty
We need to Breaks: snapd (<< 2.23.1~) to ensure this is upgraded before the new breaking kernels can hit. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-meta (Ubuntu) ** Changed in: linux-meta (Ubuntu) Status: New => Confirmed ** Changed in: linux-meta (Ubuntu) Importance: Undecided => High ** Changed in: linux-meta (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) -- 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/1666897 Title: snaps with classic + jailmode confinement started to fail on zesty Status in snapd: Fix Released Status in linux-meta package in Ubuntu: Confirmed Bug description: We just noticed that zesty stated to fail when a snap using classic confinement is installed in jailmode. $ snap install --jailmode --classic python0 $ python0 (doesn't work) /snap/python0/2/usr/bin/python0: error while loading shared libraries: libm.so.6: failed to map segment from shared object And in the system log you can see: [ 2929.841318] audit: type=1400 audit(1487770576.927:40): apparmor="DENIED" operation="file_mmap" profile="snap.python0.python0" name="/snap/core/1264/lib/x86_64-linux-gnu/libm-2.23.so" pid=5235 comm="python0" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1666897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp