Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
High
|
Colin Ian King | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
== SRU Justification ==
When running the Ubuntu nbd autotest regression test we trip a hang
and then a little later a panic message. There are two upstream
fixes required as this is actually two issues in one. One fix is to
not to shutdown the sock when IRQs are disable and a second to fix is
to race in the nbd ioctl.
== Fix ==
Upstream commits:
23272a6754b81ff
nbd: Remove signal usage
1f7b5cf1be4351e
nbd: Timeouts are not user requested disconnects
0e4f0f6f63d3416
nbd: Cleanup reset of nbd and bdev after a disconnect
c261189862c6f65
nbd: don't shutdown sock with irq's disabled
97240963eb308d8
nbd: fix race in ioctl
The first 3 patches are prerequisites required for the latter two fixes to apply and work correctly. Most of these backports are minor patch wiggles
required because later patches have been applied to the driver in earlier fixes to this driver.
== Regression Potential ==
These fixes just touch nbd, so the regression potential is just limited to this. Secondly, we are pulling in upstream fixes that exist in Bionic and Cosmic kernels, so these are tried and tested fixes.
== Test Case ==
1. Deploy a node with 4.4 Xenial
2. Run the ubuntu_
Without the fix, we get hang/crashes. With the fix one can run this test
multiple times without any issues at all.
----
This issue can be reproduced on AMD64 KVM //bare-metal node, s390x zKVM node
The test itself will pass, but the system will hang after a few second.
Steps:
1. Deploy a node with 4.4 Xenial
2. Run the ubuntu_
If you have access to the console, you will see that this system actually bumped into a kernel panic:
Unable to handle kernel pointer dereference in virtual kernel address space
failing address: 000003ff802c1000 TEID: 000003ff802c1803
Fault in home space mode while using kernel ASCE.
Log here (s390x KVM): https:/
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.4.0-136-generic s390x
NonfreeKernelMo
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Thu Sep 20 03:46:00 2018
HibernationDevice: RESUME=
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=
RelatedPackageV
linux-
linux-
linux-firmware 1.157.20
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
CVE References
description: | updated |
description: | updated |
tags: | added: i386 |
Changed in linux (Ubuntu Xenial): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in ubuntu-kernel-tests: | |
status: | New → 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 1793464
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.