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
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
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
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
** 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://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
** 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.
** 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.
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,
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
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:
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
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
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
#
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
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.
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
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
18 matches
Mail list logo