This bug was fixed in the package linux - 4.4.0-75.96
---
linux (4.4.0-75.96) xenial; urgency=low
* linux: 4.4.0-75.96 -proposed tracker (LP: #1684441)
* [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move wai
This bug was fixed in the package linux - 4.8.0-49.52
---
linux (4.8.0-49.52) yakkety; urgency=low
* linux: 4.8.0-49.52 -proposed tracker (LP: #1684427)
* [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move wa
Same test setup as above, but using yakkety with kernel
4.8.0-46-generic, reproduces the kernel oops. After upgrading to kernel
4.8.0-48-generic, the kernel oops no longer happens when modprobing or
rmmoding br_netfilter.
** Tags removed: verification-needed-xenial verification-needed-yakkety
**
With a virsh guest installed with standard xenial, using the
4.4.0-72-generic kernel, I created a bridge and attached the virtio
interface to it. I then started iperf3 -s on the guest, and started
iperf3 -c GUESTIP -t 300 on the host, to create continuous traffic to
the guest.
Then I added a simp
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 'verifica
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 'verifi
This bug was fixed in the package linux - 4.10.0-15.17
---
linux (4.10.0-15.17) zesty; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1675868
* In ZZ-BML (POWER9):ubuntu17.04 installation Fails (LP: #1675771)
- powerpc/64s: fix handling of non-synchronous ma
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => 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/1672470
Title:
ip_rcv_finish() NULL pointer kernel panic
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => 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/1672470
Title:
ip_rcv_finish() NULL pointer kernel panic
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => 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/1672470
Title:
ip_rcv_finish() NULL pointer kernel panic
S
** Description changed:
+ [Impact]
+
+ When using iptables rules affecting bridge traffic, and if affected
+ traffic is flowing through bridge while br_netfilter module is loaded or
+ unloaded, a kernel panic may occur.
+
+ [Test Case]
+
+ It's difficult to reproduce because of a very small rac
I verified the Trusty kernel isn't affected, this only applies to Xenial
and later.
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Yakkety)
Status: Confirmed
** No longer affects: linux (Ubuntu Vivid)
--
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/1672470
Title:
ip_rcv_finish() NULL pointer kernel panic
Status in linux package in Ubuntu:
I
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Yakkety)
Impor
14 matches
Mail list logo
