| 2017-11-02 16:10:37 |
Fabian Holler |
bug |
|
|
added bug |
| 2017-11-02 16:11:28 |
Fabian Holler |
attachment added |
|
Kernel log from Oops with linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002525/+files/kernoops-4.4.0-93.txt |
|
| 2017-11-02 16:11:57 |
Fabian Holler |
attachment added |
|
Kernel log from Oops with linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002526/+files/kernoops-4.10.0-32.txt |
|
| 2017-11-02 16:13:07 |
Fabian Holler |
attachment added |
|
Kernel log from Oops with linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002527/+files/kernoops-4.11.0-14.txt |
|
| 2017-11-02 16:30:23 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2017-11-03 09:54:29 |
Fabian Holler |
tags |
|
apport-collected uec-images xenial |
|
| 2017-11-03 09:54:31 |
Fabian Holler |
description |
When running 2 docker containers, one as samba server and another one as samba client that mounts and umounts a smb share a kernel OOps can be triggered on multiple kernels.
The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
shows up, some minutes later the oops and/or warnings happens.
The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop
I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with:
- linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
- linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
- linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1
In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on:
- linux-image-4.10.0-1004-gcp
- linux-image-4.12.10-041210-generic=4.12.10-041210.20170830
I haven't tried again to reproduce it with those kernels on a clean Ubuntu
installation and unfortunately didn't kept the kernel logs.
The "unregister_netdevice: waiting for lo to become free. Usage count = 1" messages are related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is handled as separate issue.
According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
https://patchwork.ozlabs.org/patch/801533/
https://patchwork.ozlabs.org/patch/778449/ |
When running 2 docker containers, one as samba server and another one as samba client that mounts and umounts a smb share a kernel OOps can be triggered on multiple kernels.
The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
shows up, some minutes later the oops and/or warnings happens.
The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop
I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with:
- linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
- linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
- linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1
In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on:
- linux-image-4.10.0-1004-gcp
- linux-image-4.12.10-041210-generic=4.12.10-041210.20170830
I haven't tried again to reproduce it with those kernels on a clean Ubuntu
installation and unfortunately didn't kept the kernel logs.
The "unregister_netdevice: waiting for lo to become free. Usage count = 1" messages are related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is handled as separate issue.
According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
https://patchwork.ozlabs.org/patch/801533/
https://patchwork.ozlabs.org/patch/778449/
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Nov 3 09:51 seq
crw-rw---- 1 root audio 116, 33 Nov 3 09:51 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Google Google Compute Engine
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y console=ttyS0
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
RelatedPackageVersions:
linux-restricted-modules-4.10.0-37-generic N/A
linux-backports-modules-4.10.0-37-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial uec-images xenial uec-images
Uname: Linux 4.10.0-37-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Google
dmi.bios.version: Google
dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
dmi.board.name: Google Compute Engine
dmi.board.vendor: Google
dmi.chassis.type: 1
dmi.chassis.vendor: Google
dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
dmi.product.name: Google Compute Engine
dmi.sys.vendor: Google |
|
| 2017-11-03 09:54:32 |
Fabian Holler |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/1729637/+attachment/5002896/+files/CurrentDmesg.txt |
|
| 2017-11-03 09:54:34 |
Fabian Holler |
attachment added |
|
JournalErrors.txt https://bugs.launchpad.net/bugs/1729637/+attachment/5002897/+files/JournalErrors.txt |
|
| 2017-11-03 09:54:35 |
Fabian Holler |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/1729637/+attachment/5002898/+files/Lspci.txt |
|
| 2017-11-03 09:54:36 |
Fabian Holler |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1729637/+attachment/5002899/+files/ProcCpuinfoMinimal.txt |
|
| 2017-11-03 09:54:38 |
Fabian Holler |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/1729637/+attachment/5002900/+files/ProcInterrupts.txt |
|
| 2017-11-03 09:54:41 |
Fabian Holler |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/1729637/+attachment/5002901/+files/ProcModules.txt |
|
| 2017-11-03 09:54:42 |
Fabian Holler |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/1729637/+attachment/5002902/+files/UdevDb.txt |
|
| 2017-11-03 09:54:44 |
Fabian Holler |
attachment added |
|
WifiSyslog.txt https://bugs.launchpad.net/bugs/1729637/+attachment/5002903/+files/WifiSyslog.txt |
|
| 2017-11-03 09:56:56 |
Fabian Holler |
attachment added |
|
Logs from kernel Oops on linux-image-4.10.0-37-generic=4.10.0-37.41~16.04.1 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002904/+files/kern.log |
|
| 2017-11-03 09:57:13 |
Fabian Holler |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2017-11-03 17:16:37 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-11-03 17:19:06 |
Joseph Salisbury |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-11-03 17:19:06 |
Joseph Salisbury |
bug task added |
|
linux (Ubuntu Zesty) |
|
| 2017-11-03 17:19:06 |
Joseph Salisbury |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-11-03 17:19:06 |
Joseph Salisbury |
bug task added |
|
linux (Ubuntu Xenial) |
|
| 2017-11-03 17:19:13 |
Joseph Salisbury |
linux (Ubuntu Xenial): status |
New |
Triaged |
|
| 2017-11-03 17:19:17 |
Joseph Salisbury |
linux (Ubuntu Zesty): status |
New |
Triaged |
|
| 2017-11-03 17:19:20 |
Joseph Salisbury |
linux (Ubuntu): status |
Confirmed |
Triaged |
|
| 2017-11-03 17:19:23 |
Joseph Salisbury |
linux (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2017-11-03 17:19:25 |
Joseph Salisbury |
linux (Ubuntu Zesty): importance |
Undecided |
Medium |
|
| 2017-11-03 18:02:10 |
Joseph Salisbury |
linux (Ubuntu): status |
Triaged |
In Progress |
|
| 2017-11-03 18:02:13 |
Joseph Salisbury |
linux (Ubuntu Xenial): status |
Triaged |
In Progress |
|
| 2017-11-03 18:02:15 |
Joseph Salisbury |
linux (Ubuntu Zesty): status |
Triaged |
In Progress |
|
| 2017-11-03 18:02:18 |
Joseph Salisbury |
linux (Ubuntu): assignee |
|
Joseph Salisbury (jsalisbury) |
|
| 2017-11-03 18:02:22 |
Joseph Salisbury |
linux (Ubuntu Xenial): assignee |
|
Joseph Salisbury (jsalisbury) |
|
| 2017-11-03 18:02:25 |
Joseph Salisbury |
linux (Ubuntu Zesty): assignee |
|
Joseph Salisbury (jsalisbury) |
|
| 2017-11-08 20:47:44 |
Joseph Salisbury |
description |
When running 2 docker containers, one as samba server and another one as samba client that mounts and umounts a smb share a kernel OOps can be triggered on multiple kernels.
The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
shows up, some minutes later the oops and/or warnings happens.
The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop
I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with:
- linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
- linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
- linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1
In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on:
- linux-image-4.10.0-1004-gcp
- linux-image-4.12.10-041210-generic=4.12.10-041210.20170830
I haven't tried again to reproduce it with those kernels on a clean Ubuntu
installation and unfortunately didn't kept the kernel logs.
The "unregister_netdevice: waiting for lo to become free. Usage count = 1" messages are related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is handled as separate issue.
According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
https://patchwork.ozlabs.org/patch/801533/
https://patchwork.ozlabs.org/patch/778449/
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Nov 3 09:51 seq
crw-rw---- 1 root audio 116, 33 Nov 3 09:51 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Google Google Compute Engine
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y console=ttyS0
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
RelatedPackageVersions:
linux-restricted-modules-4.10.0-37-generic N/A
linux-backports-modules-4.10.0-37-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial uec-images xenial uec-images
Uname: Linux 4.10.0-37-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Google
dmi.bios.version: Google
dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
dmi.board.name: Google Compute Engine
dmi.board.vendor: Google
dmi.chassis.type: 1
dmi.chassis.vendor: Google
dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
dmi.product.name: Google Compute Engine
dmi.sys.vendor: Google |
== SRU Justification ==
This bug causes Samba mount and umounts in docker container to trigger
a kernel Oops. When running 2 docker containers, one as samba server and
another one as samba client that mounts and umounts a smb share a kernel
OOps can be triggered.
This bug happens in Xenial and Zesty, and is fixed by the following two commits:
76da0704507b ("ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER")
12d94a804946 ("ipv6: fix NULL dereference in ip6_route_dev_notify()")
Both commits are clean cherry picks. 76da0704507b is in mainline as of v4.12.
Commit 12d94a804946 is in mainline as of v4.13-rc6.
== Fixes ==
commit 76da0704507bbc51875013f6557877ab308cfd0a
Author: WANG Cong <xiyou.wangcong at gmail.com>
Date: Tue Jun 20 11:42:27 2017 -0700
ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
commit 12d94a804946af291e24b80fc53ec86264765781
Author: Eric Dumazet <edumazet at google.com>
Date: Tue Aug 15 04:09:51 2017 -0700
ipv6: fix NULL dereference in ip6_route_dev_notify()
== Regression Potential ==
Both commits are specific to ipv6 and fix a regression introduced into Xenial and Zesty.
== Test Case ==
A test kernel was built with these patches and tested by the original bug reporter.
The bug reporter states the test kernel resolved the bug.
The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
shows up, some minutes later the oops and/or warnings happens.
The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop
I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with:
- linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
- linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
- linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1
In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on:
- linux-image-4.10.0-1004-gcp
- linux-image-4.12.10-041210-generic=4.12.10-041210.20170830
I haven't tried again to reproduce it with those kernels on a clean Ubuntu
installation and unfortunately didn't kept the kernel logs.
The "unregister_netdevice: waiting for lo to become free. Usage count = 1" messages are related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is handled as separate issue.
According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
https://patchwork.ozlabs.org/patch/801533/
https://patchwork.ozlabs.org/patch/778449/
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Nov 3 09:51 seq
crw-rw---- 1 root audio 116, 33 Nov 3 09:51 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Google Google Compute Engine
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y console=ttyS0
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
RelatedPackageVersions:
linux-restricted-modules-4.10.0-37-generic N/A
linux-backports-modules-4.10.0-37-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial uec-images xenial uec-images
Uname: Linux 4.10.0-37-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Google
dmi.bios.version: Google
dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
dmi.board.name: Google Compute Engine
dmi.board.vendor: Google
dmi.chassis.type: 1
dmi.chassis.vendor: Google
dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
dmi.product.name: Google Compute Engine
dmi.sys.vendor: Google |
|
| 2017-11-20 10:25:33 |
Stefan Bader |
linux (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-11-20 10:25:36 |
Stefan Bader |
linux (Ubuntu Zesty): status |
In Progress |
Fix Committed |
|
| 2017-11-28 17:47:44 |
Khaled El Mously |
tags |
apport-collected uec-images xenial |
apport-collected uec-images verification-needed-xenial xenial |
|
| 2017-11-28 17:48:13 |
Khaled El Mously |
tags |
apport-collected uec-images verification-needed-xenial xenial |
apport-collected uec-images verification-needed-xenial verification-needed-zesty xenial |
|
| 2017-11-30 16:59:20 |
Fabian Holler |
tags |
apport-collected uec-images verification-needed-xenial verification-needed-zesty xenial |
apport-collected uec-images verification-done-xenial verification-done-zesty xenial |
|
| 2017-12-07 17:43:17 |
Launchpad Janitor |
linux (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-12-07 17:43:17 |
Launchpad Janitor |
cve linked |
|
2017-1000405 |
|
| 2017-12-07 17:43:17 |
Launchpad Janitor |
cve linked |
|
2017-12146 |
|
| 2017-12-07 17:43:17 |
Launchpad Janitor |
cve linked |
|
2017-16939 |
|
| 2017-12-07 17:43:39 |
Launchpad Janitor |
linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2018-11-13 12:11:17 |
Joseph Salisbury |
linux (Ubuntu): status |
In Progress |
Fix Released |
|
| 2019-07-24 21:07:47 |
Brad Figg |
tags |
apport-collected uec-images verification-done-xenial verification-done-zesty xenial |
apport-collected cscc uec-images verification-done-xenial verification-done-zesty xenial |
|
