[Kernel-packages] [Bug 1616193] Re: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1616193 Title: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0 Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Bug description: [Impact] * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc. * Gratuitous stack trace. libvirtd: page allocation failure: order:4, mode:0x1040d0 CPU: 14 PID: 82768 Comm: libvirtd Not tainted 3.13.0-85-generic #129-Ubuntu Hardware name: Dell Inc. PowerEdge R730/0599V5, BIOS 1.5.4 10/002/2015 88003b419990 8172b6a7 001040d0 88003b419a18 811580eb 88187fffce48 88003b4199b8 8115abd6 88003b4199e8 0286 Call Trace: [] dump_stack+0x64/0x82 [] warn_alloc_failed+0xeb/0x140 [] ? drain_local_pages+0x16/0x20 [] __alloc_pages_nodemask+0x980/0xb90 [] alloc_pages_current+0xa3/0x160 [] __get_free_pages+0xe/0x50 [] kmalloc_order_trace+0x2e/0xc0 [] vhost_net_open+0x29/0x1b0 [vhost_net] [] misc_open+0xb3/0x170 [] chrdev_open+0x9f/0x1d0 [] do_dentry_open+0x233/0x2e0 [] ? cdev_put+0x30/0x30 [] vfs_open+0x49/0x50 [] do_last+0x562/0x1370 [] path_openat+0xbb/0x670 [] do_filp_open+0x3a/0x90 [] ? __alloc_fd+0xa7/0x130 [] do_sys_open+0x129/0x2a0 [] SyS_open+0x1e/0x20 [] system_call_fastpath+0x1a/0x1f * justification: because cloud. * The patches fix this issue by allowing vhost_net_open to use vmalloc when kmalloc fails to find a sufficient page size. [Test Case] * Fragment Kernel memory. Write to Nic from within a kvm guest that uses a virtio nic. [Regression Potential] * Fix was implemented upstream in 3.15, and still exists. * The fix is fairly straightfoward given the stack trace and the upstream fix. * The fix is hard to verify, as it requires significant memory fragmentation, and an over-active guest. The users machine that was experiencing this has worked around this by removing VM's from the compute host, and using vfs.cache.pressure=600. [Other Info] * https://lkml.org/lkml/2013/1/23/492 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=23cc5a991c7a9fb7e6d6550e65cee4f4173111c5 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d04257b07f2362d4eb550952d5bf5f4241a8046d * I'm going on vacation, and Eric Desrochers will be following up on this in my absence. This is also the reason for submitting before receiving verification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616193/+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 1616193] Re: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0
** Tags added: cscc -- 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/1616193 Title: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Released Bug description: [Impact] * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc. * Gratuitous stack trace. libvirtd: page allocation failure: order:4, mode:0x1040d0 CPU: 14 PID: 82768 Comm: libvirtd Not tainted 3.13.0-85-generic #129-Ubuntu Hardware name: Dell Inc. PowerEdge R730/0599V5, BIOS 1.5.4 10/002/2015 88003b419990 8172b6a7 001040d0 88003b419a18 811580eb 88187fffce48 88003b4199b8 8115abd6 88003b4199e8 0286 Call Trace: [] dump_stack+0x64/0x82 [] warn_alloc_failed+0xeb/0x140 [] ? drain_local_pages+0x16/0x20 [] __alloc_pages_nodemask+0x980/0xb90 [] alloc_pages_current+0xa3/0x160 [] __get_free_pages+0xe/0x50 [] kmalloc_order_trace+0x2e/0xc0 [] vhost_net_open+0x29/0x1b0 [vhost_net] [] misc_open+0xb3/0x170 [] chrdev_open+0x9f/0x1d0 [] do_dentry_open+0x233/0x2e0 [] ? cdev_put+0x30/0x30 [] vfs_open+0x49/0x50 [] do_last+0x562/0x1370 [] path_openat+0xbb/0x670 [] do_filp_open+0x3a/0x90 [] ? __alloc_fd+0xa7/0x130 [] do_sys_open+0x129/0x2a0 [] SyS_open+0x1e/0x20 [] system_call_fastpath+0x1a/0x1f * justification: because cloud. * The patches fix this issue by allowing vhost_net_open to use vmalloc when kmalloc fails to find a sufficient page size. [Test Case] * Fragment Kernel memory. Write to Nic from within a kvm guest that uses a virtio nic. [Regression Potential] * Fix was implemented upstream in 3.15, and still exists. * The fix is fairly straightfoward given the stack trace and the upstream fix. * The fix is hard to verify, as it requires significant memory fragmentation, and an over-active guest. The users machine that was experiencing this has worked around this by removing VM's from the compute host, and using vfs.cache.pressure=600. [Other Info] * https://lkml.org/lkml/2013/1/23/492 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=23cc5a991c7a9fb7e6d6550e65cee4f4173111c5 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d04257b07f2362d4eb550952d5bf5f4241a8046d * I'm going on vacation, and Eric Desrochers will be following up on this in my absence. This is also the reason for submitting before receiving verification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616193/+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 1616193] Re: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0
** Description changed: [Impact] * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc. * Gratuitous stack trace. libvirtd: page allocation failure: order:4, mode:0x1040d0 CPU: 14 PID: 82768 Comm: libvirtd Not tainted 3.13.0-85-generic #129-Ubuntu Hardware name: Dell Inc. PowerEdge R730/0599V5, BIOS 1.5.4 10/002/2015 88003b419990 8172b6a7 001040d0 88003b419a18 811580eb 88187fffce48 88003b4199b8 8115abd6 88003b4199e8 0286 Call Trace: [] dump_stack+0x64/0x82 [] warn_alloc_failed+0xeb/0x140 [] ? drain_local_pages+0x16/0x20 [] __alloc_pages_nodemask+0x980/0xb90 [] alloc_pages_current+0xa3/0x160 [] __get_free_pages+0xe/0x50 [] kmalloc_order_trace+0x2e/0xc0 [] vhost_net_open+0x29/0x1b0 [vhost_net] [] misc_open+0xb3/0x170 [] chrdev_open+0x9f/0x1d0 [] do_dentry_open+0x233/0x2e0 [] ? cdev_put+0x30/0x30 [] vfs_open+0x49/0x50 [] do_last+0x562/0x1370 [] path_openat+0xbb/0x670 [] do_filp_open+0x3a/0x90 [] ? __alloc_fd+0xa7/0x130 [] do_sys_open+0x129/0x2a0 [] SyS_open+0x1e/0x20 [] system_call_fastpath+0x1a/0x1f * justification: because cloud. * The patches fix this issue by allowing vhost_net_open to use vmalloc when kmalloc fails to find a sufficient page size. [Test Case] * Fragment Kernel memory. Write to Nic from within a kvm guest that uses a virtio nic. [Regression Potential] * Fix was implemented upstream in 3.15, and still exists. - * The fix is fairly straightfoward given the stack trace and the + * The fix is fairly straightfoward given the stack trace and the upstream fix. * The fix is hard to verify, as it requires significant memory fragmentation, and an over-active guest. The users machine that was experiencing this has worked around this by removing VM's from the compute host, and using vfs.cache.pressure=600. [Other Info] * https://lkml.org/lkml/2013/1/23/492 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=23cc5a991c7a9fb7e6d6550e65cee4f4173111c5 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d04257b07f2362d4eb550952d5bf5f4241a8046d - * I'm going on vacation, and Eric Desrochers will be following up on this in my absence. This is also the reason for submitting before receiving verification. + * I'm going on vacation, and Eric Desrochers will be following up on this in my absence. This is also the reason for submitting before receiving verification. -- 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/1616193 Title: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Released Bug description: [Impact] * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc. * Gratuitous stack trace. libvirtd: page allocation failure: order:4, mode:0x1040d0 CPU: 14 PID: 82768 Comm: libvirtd Not tainted 3.13.0-85-generic #129-Ubuntu Hardware name: Dell Inc. PowerEdge R730/0599V5, BIOS 1.5.4 10/002/2015 88003b419990 8172b6a7 001040d0 88003b419a18 811580eb 88187fffce48 88003b4199b8 8115abd6 88003b4199e8 0286 Call Trace: [] dump_stack+0x64/0x82 [] warn_alloc_failed+0xeb/0x140 [] ? drain_local_pages+0x16/0x20 [] __alloc_pages_nodemask+0x980/0xb90 [] alloc_pages_current+0xa3/0x160 [] __get_free_pages+0xe/0x50 [] kmalloc_order_trace+0x2e/0xc0 [] vhost_net_open+0x29/0x1b0 [vhost_net] [] misc_open+0xb3/0x170 [] chrdev_open+0x9f/0x1d0 [] do_dentry_open+0x233/0x2e0 [] ? cdev_put+0x30/0x30 [] vfs_open+0x49/0x50 [] do_last+0x562/0x1370 [] path_openat+0xbb/0x670 [] do_filp_open+0x3a/0x90 [] ? __alloc_fd+0xa7/0x130 [] do_sys_open+0x129/0x2a0 [] SyS_open+0x1e/0x20 [] system_call_fastpath+0x1a/0x1f * justification: because cloud. * The patches fix this issue by allowing vhost_net_open to use vmalloc when kmalloc fails to find a sufficient page size. [Test Case] * Fragment Kernel memory. Write to Nic from within a kvm guest that uses a virtio nic. [Regression Potential] * Fix was implemented upstream in 3.15, and still exists. * The fix is fairly straightfoward given the stack trace and the upstream fix. * The fix is hard to verify, as it requires significant memory fragmentation, and
[Kernel-packages] [Bug 1616193] Re: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0
This bug was fixed in the package linux - 3.13.0-96.143 --- linux (3.13.0-96.143) trusty; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1618083 * CVE-2015-8767 - sctp: Prevent soft lockup when sctp_accept() is called during a timeout event * MacBookPro11,4 fails to poweroff or suspend (LP: #1587714) - SAUCE: PCI: Workaround to enable poweroff on Mac Pro 11 * 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0 (LP: #1616193) - vhost-net: extend device allocation to vmalloc - vhost-net: don't open-code kvfree * [arm64] nova instances can't boot with 3.13.0-92 (LP: #1608854) - Revert "UBUNTU: [Config] CONFIG_EFI=n for arm64" - Revert "UBUNTU: SAUCE: UEFI: Set EFI_SECURE_BOOT bit in x86_efi_facility" - Revert "UBUNTU: SAUCE: UEFI: Add secure boot and MOK SB State disabled sysctl" - Revert "UBUNTU: SAUCE: UEFI: Display MOKSBState when disabled" - Revert "UBUNTU: SAUCE: UEFI: efi: Disable secure boot if shim is in insecure mode" - Revert "UBUNTU: SAUCE: UEFI MODSIGN: Import certificates from UEFI Secure Boot" - Revert "UBUNTU: SAUCE: UEFI: efi: Make EFI_SECURE_BOOT_SIG_ENFORCE depend on EFI" - Revert "UBUNTU: SAUCE: UEFI: Add option to automatically enforce module signatures when in Secure Boot mode" - Revert "UBUNTU: [Config] CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y" - Revert "UBUNTU: SAUCE: UEFI: x86: Restrict MSR access when module loading is restricted" - Revert "UBUNTU: SAUCE: UEFI: kexec: Disable at runtime if the kernel enforces module loading restrictions" - Revert "UBUNTU: SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module loading is restricted" - Revert "UBUNTU: SAUCE: UEFI: Restrict /dev/mem and /dev/kmem when module loading is restricted" - Revert "UBUNTU: SAUCE: UEFI: asus-wmi: Restrict debugfs interface when module loading is restricted" - Revert "UBUNTU: SAUCE: UEFI: ACPI: Limit access to custom_method" - Revert "UBUNTU: SAUCE: UEFI: x86: Lock down IO port access when module security is enabled" - Revert "UBUNTU: SAUCE: UEFI: PCI: Lock down BAR access when module security is enabled" - Revert "UBUNTU: SAUCE: UEFI: Add secure_modules() call" - Revert "x86/efi: Build our own EFI services pointer table" - Revert "efi: Add separate 32-bit/64-bit definitions" * [Hyper-V] storvsc messages for CD-ROM medium not present tray closed (LP: #1590655) - scsi: storvsc: Filter out storvsc messages CD-ROM medium not present * CVE-2016-3841 - ipv6: add complete rcu protection around np->opt -- Kamal Mostafa Tue, 16 Aug 2016 10:20:51 -0700 ** Changed in: linux (Ubuntu Trusty) Status: Fix Committed => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2015-8767 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-3841 -- 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/1616193 Title: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Released Bug description: [Impact] * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc. * Gratuitous stack trace. libvirtd: page allocation failure: order:4, mode:0x1040d0 CPU: 14 PID: 82768 Comm: libvirtd Not tainted 3.13.0-85-generic #129-Ubuntu Hardware name: Dell Inc. PowerEdge R730/0599V5, BIOS 1.5.4 10/002/2015 88003b419990 8172b6a7 001040d0 88003b419a18 811580eb 88187fffce48 88003b4199b8 8115abd6 88003b4199e8 0286 Call Trace: [] dump_stack+0x64/0x82 [] warn_alloc_failed+0xeb/0x140 [] ? drain_local_pages+0x16/0x20 [] __alloc_pages_nodemask+0x980/0xb90 [] alloc_pages_current+0xa3/0x160 [] __get_free_pages+0xe/0x50 [] kmalloc_order_trace+0x2e/0xc0 [] vhost_net_open+0x29/0x1b0 [vhost_net] [] misc_open+0xb3/0x170 [] chrdev_open+0x9f/0x1d0 [] do_dentry_open+0x233/0x2e0 [] ? cdev_put+0x30/0x30 [] vfs_open+0x49/0x50 [] do_last+0x562/0x1370 [] path_openat+0xbb/0x670 [] do_filp_open+0x3a/0x90 [] ? __alloc_fd+0xa7/0x130 [] do_sys_open+0x129/0x2a0 [] SyS_open+0x1e/0x20 [] system_call_fastpath+0x1a/0x1f * justification: because cloud. * The patches fix this issue by allowing vhost_net_open to use vmalloc when kmalloc fails to find a sufficient page size. [Test Case] * Fragment Kernel memory. Write to Nic from within a kvm guest that uses a virtio nic. [Regression Potential] * Fix was implemented u
[Kernel-packages] [Bug 1616193] Re: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0
Marking verification-done-trusty, as the user has not replied back to me one way or the other so I'll assume their kernel is no longer getting allocation errors. I definitely don't want this pulled from the sources prematurely. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- 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/1616193 Title: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Committed Bug description: [Impact] * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc. * Gratuitous stack trace. libvirtd: page allocation failure: order:4, mode:0x1040d0 CPU: 14 PID: 82768 Comm: libvirtd Not tainted 3.13.0-85-generic #129-Ubuntu Hardware name: Dell Inc. PowerEdge R730/0599V5, BIOS 1.5.4 10/002/2015 88003b419990 8172b6a7 001040d0 88003b419a18 811580eb 88187fffce48 88003b4199b8 8115abd6 88003b4199e8 0286 Call Trace: [] dump_stack+0x64/0x82 [] warn_alloc_failed+0xeb/0x140 [] ? drain_local_pages+0x16/0x20 [] __alloc_pages_nodemask+0x980/0xb90 [] alloc_pages_current+0xa3/0x160 [] __get_free_pages+0xe/0x50 [] kmalloc_order_trace+0x2e/0xc0 [] vhost_net_open+0x29/0x1b0 [vhost_net] [] misc_open+0xb3/0x170 [] chrdev_open+0x9f/0x1d0 [] do_dentry_open+0x233/0x2e0 [] ? cdev_put+0x30/0x30 [] vfs_open+0x49/0x50 [] do_last+0x562/0x1370 [] path_openat+0xbb/0x670 [] do_filp_open+0x3a/0x90 [] ? __alloc_fd+0xa7/0x130 [] do_sys_open+0x129/0x2a0 [] SyS_open+0x1e/0x20 [] system_call_fastpath+0x1a/0x1f * justification: because cloud. * The patches fix this issue by allowing vhost_net_open to use vmalloc when kmalloc fails to find a sufficient page size. [Test Case] * Fragment Kernel memory. Write to Nic from within a kvm guest that uses a virtio nic. [Regression Potential] * Fix was implemented upstream in 3.15, and still exists. * The fix is fairly straightfoward given the stack trace and the upstream fix. * The fix is hard to verify, as it requires significant memory fragmentation, and an over-active guest. The users machine that was experiencing this has worked around this by removing VM's from the compute host, and using vfs.cache.pressure=600. [Other Info] * https://lkml.org/lkml/2013/1/23/492 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=23cc5a991c7a9fb7e6d6550e65cee4f4173111c5 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d04257b07f2362d4eb550952d5bf5f4241a8046d * I'm going on vacation, and Eric Desrochers will be following up on this in my absence. This is also the reason for submitting before receiving verification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616193/+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 1616193] Re: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0
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! ** Tags added: verification-needed-trusty -- 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/1616193 Title: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Committed Bug description: [Impact] * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc. * Gratuitous stack trace. libvirtd: page allocation failure: order:4, mode:0x1040d0 CPU: 14 PID: 82768 Comm: libvirtd Not tainted 3.13.0-85-generic #129-Ubuntu Hardware name: Dell Inc. PowerEdge R730/0599V5, BIOS 1.5.4 10/002/2015 88003b419990 8172b6a7 001040d0 88003b419a18 811580eb 88187fffce48 88003b4199b8 8115abd6 88003b4199e8 0286 Call Trace: [] dump_stack+0x64/0x82 [] warn_alloc_failed+0xeb/0x140 [] ? drain_local_pages+0x16/0x20 [] __alloc_pages_nodemask+0x980/0xb90 [] alloc_pages_current+0xa3/0x160 [] __get_free_pages+0xe/0x50 [] kmalloc_order_trace+0x2e/0xc0 [] vhost_net_open+0x29/0x1b0 [vhost_net] [] misc_open+0xb3/0x170 [] chrdev_open+0x9f/0x1d0 [] do_dentry_open+0x233/0x2e0 [] ? cdev_put+0x30/0x30 [] vfs_open+0x49/0x50 [] do_last+0x562/0x1370 [] path_openat+0xbb/0x670 [] do_filp_open+0x3a/0x90 [] ? __alloc_fd+0xa7/0x130 [] do_sys_open+0x129/0x2a0 [] SyS_open+0x1e/0x20 [] system_call_fastpath+0x1a/0x1f * justification: because cloud. * The patches fix this issue by allowing vhost_net_open to use vmalloc when kmalloc fails to find a sufficient page size. [Test Case] * Fragment Kernel memory. Write to Nic from within a kvm guest that uses a virtio nic. [Regression Potential] * Fix was implemented upstream in 3.15, and still exists. * The fix is fairly straightfoward given the stack trace and the upstream fix. * The fix is hard to verify, as it requires significant memory fragmentation, and an over-active guest. The users machine that was experiencing this has worked around this by removing VM's from the compute host, and using vfs.cache.pressure=600. [Other Info] * https://lkml.org/lkml/2013/1/23/492 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=23cc5a991c7a9fb7e6d6550e65cee4f4173111c5 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d04257b07f2362d4eb550952d5bf5f4241a8046d * I'm going on vacation, and Eric Desrochers will be following up on this in my absence. This is also the reason for submitting before receiving verification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616193/+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 1616193] Re: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- 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/1616193 Title: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Committed Bug description: [Impact] * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc. * Gratuitous stack trace. libvirtd: page allocation failure: order:4, mode:0x1040d0 CPU: 14 PID: 82768 Comm: libvirtd Not tainted 3.13.0-85-generic #129-Ubuntu Hardware name: Dell Inc. PowerEdge R730/0599V5, BIOS 1.5.4 10/002/2015 88003b419990 8172b6a7 001040d0 88003b419a18 811580eb 88187fffce48 88003b4199b8 8115abd6 88003b4199e8 0286 Call Trace: [] dump_stack+0x64/0x82 [] warn_alloc_failed+0xeb/0x140 [] ? drain_local_pages+0x16/0x20 [] __alloc_pages_nodemask+0x980/0xb90 [] alloc_pages_current+0xa3/0x160 [] __get_free_pages+0xe/0x50 [] kmalloc_order_trace+0x2e/0xc0 [] vhost_net_open+0x29/0x1b0 [vhost_net] [] misc_open+0xb3/0x170 [] chrdev_open+0x9f/0x1d0 [] do_dentry_open+0x233/0x2e0 [] ? cdev_put+0x30/0x30 [] vfs_open+0x49/0x50 [] do_last+0x562/0x1370 [] path_openat+0xbb/0x670 [] do_filp_open+0x3a/0x90 [] ? __alloc_fd+0xa7/0x130 [] do_sys_open+0x129/0x2a0 [] SyS_open+0x1e/0x20 [] system_call_fastpath+0x1a/0x1f * justification: because cloud. * The patches fix this issue by allowing vhost_net_open to use vmalloc when kmalloc fails to find a sufficient page size. [Test Case] * Fragment Kernel memory. Write to Nic from within a kvm guest that uses a virtio nic. [Regression Potential] * Fix was implemented upstream in 3.15, and still exists. * The fix is fairly straightfoward given the stack trace and the upstream fix. * The fix is hard to verify, as it requires significant memory fragmentation, and an over-active guest. The users machine that was experiencing this has worked around this by removing VM's from the compute host, and using vfs.cache.pressure=600. [Other Info] * https://lkml.org/lkml/2013/1/23/492 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=23cc5a991c7a9fb7e6d6550e65cee4f4173111c5 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d04257b07f2362d4eb550952d5bf5f4241a8046d * I'm going on vacation, and Eric Desrochers will be following up on this in my absence. This is also the reason for submitting before receiving verification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616193/+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 1616193] Re: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0
Fix submitted to kernel-t...@lists.ubuntu.com. ** Description changed: - [Impact] - * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc. + [Impact] + * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc. - * Gratuitous stack trace. + * Gratuitous stack trace. libvirtd: page allocation failure: order:4, mode:0x1040d0 CPU: 14 PID: 82768 Comm: libvirtd Not tainted 3.13.0-85-generic #129-Ubuntu Hardware name: Dell Inc. PowerEdge R730/0599V5, BIOS 1.5.4 10/002/2015 - 88003b419990 8172b6a7 001040d0 - 88003b419a18 811580eb 88187fffce48 - 88003b4199b8 8115abd6 88003b4199e8 0286 + 88003b419990 8172b6a7 001040d0 + 88003b419a18 811580eb 88187fffce48 + 88003b4199b8 8115abd6 88003b4199e8 0286 Call Trace: - [] dump_stack+0x64/0x82 - [] warn_alloc_failed+0xeb/0x140 - [] ? drain_local_pages+0x16/0x20 - [] __alloc_pages_nodemask+0x980/0xb90 - [] alloc_pages_current+0xa3/0x160 - [] __get_free_pages+0xe/0x50 - [] kmalloc_order_trace+0x2e/0xc0 - [] vhost_net_open+0x29/0x1b0 [vhost_net] - [] misc_open+0xb3/0x170 - [] chrdev_open+0x9f/0x1d0 - [] do_dentry_open+0x233/0x2e0 - [] ? cdev_put+0x30/0x30 - [] vfs_open+0x49/0x50 - [] do_last+0x562/0x1370 - [] path_openat+0xbb/0x670 - [] do_filp_open+0x3a/0x90 - [] ? __alloc_fd+0xa7/0x130 - [] do_sys_open+0x129/0x2a0 - [] SyS_open+0x1e/0x20 - [] system_call_fastpath+0x1a/0x1f + [] dump_stack+0x64/0x82 + [] warn_alloc_failed+0xeb/0x140 + [] ? drain_local_pages+0x16/0x20 + [] __alloc_pages_nodemask+0x980/0xb90 + [] alloc_pages_current+0xa3/0x160 + [] __get_free_pages+0xe/0x50 + [] kmalloc_order_trace+0x2e/0xc0 + [] vhost_net_open+0x29/0x1b0 [vhost_net] + [] misc_open+0xb3/0x170 + [] chrdev_open+0x9f/0x1d0 + [] do_dentry_open+0x233/0x2e0 + [] ? cdev_put+0x30/0x30 + [] vfs_open+0x49/0x50 + [] do_last+0x562/0x1370 + [] path_openat+0xbb/0x670 + [] do_filp_open+0x3a/0x90 + [] ? __alloc_fd+0xa7/0x130 + [] do_sys_open+0x129/0x2a0 + [] SyS_open+0x1e/0x20 + [] system_call_fastpath+0x1a/0x1f - * justification: cloud. + * justification: because cloud. - * The patches fix this issue by allowing vhost_net_open to use vmalloc - when kmalloc fails to find a sufficient page. + * The patches fix this issue by allowing vhost_net_open to use vmalloc + when kmalloc fails to find a sufficient page size. [Test Case] - * Fragment Kernel memory. Write to Nic from within a kvm guest that + * Fragment Kernel memory. Write to Nic from within a kvm guest that uses a virtio nic. [Regression Potential] - * Fix was implemented upstream in 3.15, and still exists. + * Fix was implemented upstream in 3.15, and still exists. - * Testing TBD + * The fix is fairly straightfoward given the stack trace and the + upstream fix. + + * The fix is hard to verify, as it requires significant memory + fragmentation, and an over-active guest. The users machine that was + experiencing this has worked around this by removing VM's from the + compute host, and using vfs.cache.pressure=600. [Other Info] - - * https://lkml.org/lkml/2013/1/23/492 - * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=23cc5a991c7a9fb7e6d6550e65cee4f4173111c5 - * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d04257b07f2362d4eb550952d5bf5f4241a8046d + + * https://lkml.org/lkml/2013/1/23/492 + * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=23cc5a991c7a9fb7e6d6550e65cee4f4173111c5 + * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d04257b07f2362d4eb550952d5bf5f4241a8046d + * I'm going on vacation, and Eric Desrochers will be following up on this in my absence. This is also the reason for submitting before receiving verification. -- 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/1616193 Title: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0 Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc. * Gratuitous stack trace. libvirtd: page allocation failure: order:4, mode:0x1040d0 CPU: 14 PID: 82768 Comm: libvirtd Not tainted 3.13.0-85-generic #129-Ubuntu Hardware name: Dell
[Kernel-packages] [Bug 1616193] Re: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0
Shut the front door bug-bot. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1616193 Title: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0 Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc. * Gratuitous stack trace. libvirtd: page allocation failure: order:4, mode:0x1040d0 CPU: 14 PID: 82768 Comm: libvirtd Not tainted 3.13.0-85-generic #129-Ubuntu Hardware name: Dell Inc. PowerEdge R730/0599V5, BIOS 1.5.4 10/002/2015 88003b419990 8172b6a7 001040d0 88003b419a18 811580eb 88187fffce48 88003b4199b8 8115abd6 88003b4199e8 0286 Call Trace: [] dump_stack+0x64/0x82 [] warn_alloc_failed+0xeb/0x140 [] ? drain_local_pages+0x16/0x20 [] __alloc_pages_nodemask+0x980/0xb90 [] alloc_pages_current+0xa3/0x160 [] __get_free_pages+0xe/0x50 [] kmalloc_order_trace+0x2e/0xc0 [] vhost_net_open+0x29/0x1b0 [vhost_net] [] misc_open+0xb3/0x170 [] chrdev_open+0x9f/0x1d0 [] do_dentry_open+0x233/0x2e0 [] ? cdev_put+0x30/0x30 [] vfs_open+0x49/0x50 [] do_last+0x562/0x1370 [] path_openat+0xbb/0x670 [] do_filp_open+0x3a/0x90 [] ? __alloc_fd+0xa7/0x130 [] do_sys_open+0x129/0x2a0 [] SyS_open+0x1e/0x20 [] system_call_fastpath+0x1a/0x1f * justification: cloud. * The patches fix this issue by allowing vhost_net_open to use vmalloc when kmalloc fails to find a sufficient page. [Test Case] * Fragment Kernel memory. Write to Nic from within a kvm guest that uses a virtio nic. [Regression Potential] * Fix was implemented upstream in 3.15, and still exists. * Testing TBD [Other Info] * https://lkml.org/lkml/2013/1/23/492 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=23cc5a991c7a9fb7e6d6550e65cee4f4173111c5 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d04257b07f2362d4eb550952d5bf5f4241a8046d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616193/+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