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 <a...@canonical.com> Fri, 05 Feb 2016 14:58:51 +0000 ** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => 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/1539349 Title: sleep from invalid context in aa_move_mount Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: In xenial master-next, when I cp /bin/mount /home/ubuntu/mount, define the following policy: #include <tunables/global> /home/ubuntu/mount { #include <abstractions/base> #include <abstractions/nameservice> capability, network, mount, /** mkrwixr, } And then run the following script under sudo from ~/ubuntu: #!/bin/sh apparmor_parser -r /home/ubuntu/mount.aa umount -l a/b umount -l a/a umount -l a rm -rf a mkdir a mount --bind a a mount --make-slave a mkdir a/a a/b mount -t tmpfs tmpfs a/a /home/ubuntu/mount --move a/a a/b I get the following kernel warning: Jan 29 02:36:06 seth kernel: audit: type=1400 audit(1454034966.022:15): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/home/ubuntu/mount" pid=1179 comm="apparmor_parser" Jan 29 02:36:06 seth kernel: BUG: sleeping function called from invalid context at mm/slub.c:1287 Jan 29 02:36:06 seth kernel: in_atomic(): 1, irqs_disabled(): 0, pid: 1189, name: mount Jan 29 02:36:06 seth kernel: no locks held by mount/1189. Jan 29 02:36:06 seth kernel: CPU: 0 PID: 1189 Comm: mount Not tainted 4.4.0+ #4 Jan 29 02:36:06 seth kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 Jan 29 02:36:06 seth kernel: 0000000000000000 00000000a02414bf ffff88007784fc28 ffffffff81449309 Jan 29 02:36:06 seth kernel: ffff880079129580 ffff88007784fc50 ffffffff810b5789 ffffffff81ce0e60 Jan 29 02:36:06 seth kernel: 0000000000000507 0000000000000000 ffff88007784fc78 ffffffff810b5889 Jan 29 02:36:06 seth kernel: Call Trace: Jan 29 02:36:06 seth kernel: [<ffffffff81449309>] dump_stack+0x4b/0x72 Jan 29 02:36:06 seth kernel: [<ffffffff810b5789>] ___might_sleep+0x179/0x230 Jan 29 02:36:06 seth kernel: [<ffffffff810b5889>] __might_sleep+0x49/0x80 Jan 29 02:36:06 seth kernel: [<ffffffff81258814>] ? getname_kernel+0x34/0x120 Jan 29 02:36:06 seth kernel: [<ffffffff81221fcb>] kmem_cache_alloc+0x1db/0x2a0 Jan 29 02:36:06 seth kernel: [<ffffffff81258814>] getname_kernel+0x34/0x120 Jan 29 02:36:06 seth kernel: [<ffffffff81258e96>] kern_path+0x16/0x30 Jan 29 02:36:06 seth kernel: [<ffffffff813e98ac>] aa_move_mount+0x17c/0x320 Jan 29 02:36:06 seth kernel: [<ffffffff813df7a3>] apparmor_sb_mount+0x233/0x2d0 Jan 29 02:36:06 seth kernel: [<ffffffff81392be7>] security_sb_mount+0x57/0x80 Jan 29 02:36:06 seth kernel: [<ffffffff8126f581>] do_mount+0xb1/0xe60 Jan 29 02:36:06 seth kernel: [<ffffffff811f0416>] ? __might_fault+0x96/0xa0 Jan 29 02:36:06 seth kernel: [<ffffffff811deae3>] ? memdup_user+0x53/0x80 Jan 29 02:36:06 seth kernel: [<ffffffff8127066f>] SyS_mount+0x9f/0x100 Jan 29 02:36:06 seth kernel: [<ffffffff818d0af6>] entry_SYSCALL_64_fastpath+0x16/0x76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539349/+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