Samba mount/umount in docker container triggers kernel Oops
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Unassigned | ||
Zesty |
Fix Released
|
Medium
|
Unassigned |
Bug Description
== 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_
12d94a804946 ("ipv6: fix NULL dereference in ip6_route_
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 76da0704507bbc5
Author: WANG Cong <xiyou.wangcong at gmail.com>
Date: Tue Jun 20 11:42:27 2017 -0700
ipv6: only call ip6_route_
commit 12d94a804946af2
Author: Eric Dumazet <edumazet at google.com>
Date: Tue Aug 15 04:09:51 2017 -0700
ipv6: fix NULL dereference in ip6_route_
== 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_
shows up, some minutes later the oops and/or warnings happens.
The scripts to trigger the kernel Oops can be found at: https:/
I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with:
- linux-image-
- linux-image-
- linux-image-
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-
- linux-image-
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_
According to https:/
https:/
https:/
---
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-
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
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.
dmi.board.name: Google Compute Engine
dmi.board.vendor: Google
dmi.chassis.type: 1
dmi.chassis.vendor: Google
dmi.modalias: dmi:bvnGoogle:
dmi.product.name: Google Compute Engine
dmi.sys.vendor: Google
CVE References
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Xenial): | |
status: | New → Triaged |
Changed in linux (Ubuntu Zesty): | |
status: | New → Triaged |
Changed in linux (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Zesty): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Zesty): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Released |
tags: | added: cscc |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1729637
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.