[Bug 1672144] Re: ifup service of network device stay active after driver stop
This bug was fixed in the package linux - 4.4.0-78.99 --- linux (4.4.0-78.99) xenial; urgency=low * linux: 4.4.0-78.99 -proposed tracker (LP: #1686645) * Please backport fix to reference leak in cgroup blkio throttle (LP: #1683976) - block: fix module reference leak on put_disk() call for cgroups throttle * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel 4.4.0-47-generic (LP: #1659111) - block: Unhash block device inodes on gendisk destruction - block: Use pointer to backing_dev_info from request_queue - block: Dynamically allocate and refcount backing_dev_info - block: Make blk_get_backing_dev_info() safe without open bdev - block: Get rid of blk_get_backing_dev_info() - block: Move bdev_unhash_inode() after invalidate_partition() - block: Unhash also block device inode for the whole device - block: Revalidate i_bdev reference in bd_aquire() - block: Initialize bd_bdi on inode initialization - block: Move bdi_unregister() to del_gendisk() - block: Allow bdi re-registration - bdi: Fix use-after-free in wb_congested_put() - block: Make del_gendisk() safer for disks without queues - block: Fix bdi assignment to bdev inode when racing with disk delete - bdi: Mark congested->bdi as internal - bdi: Make wb->bdi a proper reference - bdi: Unify bdi->wb_list handling for root wb_writeback - bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy() - bdi: Do not wait for cgwbs release in bdi_unregister() - bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister() - block: Fix oops in locked_inode_to_wb_and_lock_list() - kobject: Export kobject_get_unless_zero() - block: Fix oops scsi_disk_get() * Touchpad not working correctly after kernel upgrade (LP: #1662589) - Input: ALPS - fix V8+ protocol handling (73 03 28) * Xenial update to v4.4.62 stable release (LP: #1683728) - drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3 - drm/i915: Stop using RP_DOWN_EI on Baytrail - usb: dwc3: gadget: delay unmap of bounced requests - mtd: bcm47xxpart: fix parsing first block after aligned TRX - MIPS: Introduce irq_stack - MIPS: Stack unwinding while on IRQ stack - MIPS: Only change $28 to thread_info if coming from user mode - MIPS: Switch to the irq_stack in interrupts - MIPS: Select HAVE_IRQ_EXIT_ON_IRQ_STACK - MIPS: IRQ Stack: Fix erroneous jal to plat_irq_dispatch - crypto: caam - fix RNG deinstantiation error checking - Linux 4.4.62 * ifup service of network device stay active after driver stop (LP: #1672144) - net: use net->count to check whether a netns is alive or not * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215) - block: relax check on sg gap * [Feature] KBL: intel_powerclamp driver support (LP: #1591641) - thermal/powerclamp: remove cpu whitelist - thermal/powerclamp: correct cpu support check - thermal/powerclamp: add back module device table * sysfs channel reads of lps22hb pressure sensor are stale (LP: #1682103) - iio: st_pressure: initialize lps22hb bootime * Backlight control does not work and there are no entries in /sys/class/backlight (LP: #1667323) - Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6" * [Feature] KBL: intel_rapl driver support (LP: #1591640) - powercap/intel_rapl: Add support for Kabylake * Xenial update to v4.4.61 stable release (LP: #1682140) - drm/vmwgfx: Type-check lookups of fence objects - drm/vmwgfx: NULL pointer dereference in vmw_surface_define_ioctl() - drm/vmwgfx: avoid calling vzalloc with a 0 size in vmw_get_cap_3d_ioctl() - drm/ttm, drm/vmwgfx: Relax permission checking when opening surfaces - drm/vmwgfx: Remove getparam error message - drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl() - sysfs: be careful of error returns from ops->show() - staging: android: ashmem: lseek failed due to no FMODE_LSEEK. - arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm - arm/arm64: KVM: Take mmap_sem in kvm_arch_prepare_memory_region - iio: bmg160: reset chip when probing - Reset TreeId to zero on SMB2 TREE_CONNECT - ptrace: fix PTRACE_LISTEN race corrupting task->state - ring-buffer: Fix return value check in test_ringbuffer() - metag/usercopy: Drop unused macros - metag/usercopy: Fix alignment error checking - metag/usercopy: Add early abort to copy_to_user - metag/usercopy: Zero rest of buffer from copy_from_user - metag/usercopy: Set flags before ADDZ - metag/usercopy: Fix src fixup in from user rapf loops - metag/usercopy: Add missing fixups - powerpc/mm: Add missing global TLB invalidate if cxl is active - powerpc: Don't try to fix up misaligned load-with-reservation instructions - nios2: reserve boot memory for device tree - s390/decompressor: fix initrd corruption caused by bss cl
[Bug 1672144] Re: ifup service of network device stay active after driver stop
This bug was fixed in the package linux - 4.8.0-52.55 --- linux (4.8.0-52.55) yakkety; urgency=low * linux: 4.8.0-52.55 -proposed tracker (LP: #1686976) * CVE-2017-7477: macsec: avoid heap overflow in skb_to_sgvec (LP: #1685892) - macsec: avoid heap overflow in skb_to_sgvec - macsec: dynamically allocate space for sglist * net/ipv4: original ingress device index set as the loopback interface. (LP: #1683982) - net: fix incorrect original ingress device index in PKTINFO * Touchpad not working correctly after kernel upgrade (LP: #1662589) - Input: ALPS - fix V8+ protocol handling (73 03 28) * ifup service of network device stay active after driver stop (LP: #1672144) - net: use net->count to check whether a netns is alive or not * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215) - block: relax check on sg gap * Potential memory corruption with capi adapters (LP: #1681469) - powerpc/mm: Add missing global TLB invalidate if cxl is active * [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and image (LP: #1650058) - net/mlx4_en: Fix bad WQE issue - net/mlx4_core: Fix racy CQ (Completion Queue) free - net/mlx4_core: Fix when to save some qp context flags for dynamic VST to VGT transitions - net/mlx4_core: Avoid command timeouts during VF driver device shutdown -- Stefan Bader Fri, 28 Apr 2017 12:17:12 +0200 ** Changed in: linux (Ubuntu Yakkety) Status: Fix Committed => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-7477 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
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- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. 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-xenial ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
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- yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed- yakkety'. 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! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
https://lists.ubuntu.com/archives/kernel-team/2017-March/083374.html ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
** Changed in: linux (Ubuntu Yakkety) Status: New => In Progress ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
v4.10.5 was included in Ubuntu-4.10.0-15.17 ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: Incomplete ** Changed in: linux (Ubuntu Zesty) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
It should be included in next release of zesty kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
The issue doesn't reproduce with the 4.10.5 mainline kernel. could you please cherry-pick this commit to the zesty kernel? Thanks Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
Thank you I will give a try and update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
It works on linux 4.11-rc3.
After kernel bisect, this commit fixes the issue:
commit 91864f5852f9996210fad400cf70fb85af091243
Author: Andrey Vagin
Date: Sun Mar 12 21:36:18 2017 -0700
net: use net->count to check whether a netns is alive or not
The previous idea was to check whether a net namespace is in
net_exit_list or not. It doesn't work, because net->exit_list is used in
__register_pernet_operations and __unregister_pernet_operations where
all namespaces are added to a temporary list to make cleanup in a error
case, so list_empty(&net->exit_list) always returns false.
Reported-by: Mantas Mikulėnas
Fixes: 002d8a1a6c11 ("net: skip genenerating uevents for network namespaces
that are exiting")
Signed-off-by: Andrei Vagin
Signed-off-by: David S. Miller
And it's also included in 4.10.5 stable tree, so it'll land to 17.04's linux
kernel soon.
You can try 4.10.5 mainline kernel at here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.5/
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672144
Title:
ifup service of network device stay active after driver stop
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672144/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
This bug reproduced with tg3 , mlx4, mlx5 and bonding modules and i beleve that this issue reproduce on each interface that has ifup service. simple reproduce 1. interfaces is up after reboot or ifup. 2. modprobe -r #network interfaces closed and removed 3.systemctl status ifup@.service # service is up although the network interface doesn't exist. This issue not reproduced with kernel 4.9. when we moved to kernel 4.10 we see this issue. thanks Talat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
network interface ifup. # ifup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
Hmm, I failed to do something like `systemd enable ifup@enpXXX.service` because there's no [Install] section. Do you know which program started this service? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
No, not equal :~# systemctl cat sys-subsystem-net-devices-ens1f0.device No files found for sys-subsystem-net-devices-ens1f0.device. :~# ifup ens1f0 ifup: interface ens1f0 already configured :~# systemctl cat ifup@ens1f0.service # /lib/systemd/system/ifup@.service [Unit] Description=ifup for %I After=local-fs.target network-pre.target apparmor.service systemd-sysctl.service Before=network.target shutdown.target network-online.target Conflicts=shutdown.target BindsTo=sys-subsystem-net-devices-%i.device After=sys-subsystem-net-devices-%i.device DefaultDependencies=no IgnoreOnIsolate=yes [Service] # avoid stopping on shutdown via stopping system-ifup.slice Slice=system.slice ExecStart=/bin/sh -ec 'ifup --allow=hotplug %I; ifup --allow=auto %I; \ if ifquery %I >/dev/null; then ifquery --state %I >/dev/null; fi' ExecStop=/sbin/ifdown %I RemainAfterExit=true TimeoutStartSec=5min -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672144] Re: ifup service of network device stay active after driver stop
Does "The network device systemd service" equal to "sys-subsystem-net- devices-*.device"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672144 Title: ifup service of network device stay active after driver stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
