Intel NVMe drives timeout when nvme format is attempted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Joseph Salisbury | ||
Bionic |
Fix Released
|
Medium
|
Joseph Salisbury |
Bug Description
== SRU Justification ==
Dell reports that every time they run a nvme format on an Intel
NVMe drive (whether specifying the secure/crypto erase options or not), the
format apparently works (drive is wiped clean). The drive's admin queue
(queue 0) times out, making the nvme device driver flag an error and reset the controller.
This bug is fixed by commit 62843c2e4226, which is in mainline as of
v4.17-rc1.
== Fix ==
62843c2e4226 ("nvme: Use admin command effects for admin commands")
== Regression Potential ==
Low. Limited to nvme driver.
== Test Case ==
A test kernel was built with this patch and tested by the original bug reporter.
The bug reporter states the test kernel resolved the bug.
Every time you run an nvme format on a Intel NVMe drive (whether specifying the secure/crypto erase options or not), the format apparently works (drive is wiped clean) but the drive's admin queue (queue 0) times out, making the nvme device driver flag an error and reset the controller.
Here's an example:
nvme-cli-1.5 # ./nvme format -l 0 /dev/nvme1
NVME Admin command error:ABORT_REQ(7)
nvme-cli-1.5 # dmesg|tail -1
[79725.404910] nvme nvme1: I/O 151 QID 0 timeout, reset controller
Patch required:
https:/
Request you to include the patch for LTS kernel 4.15 of Ubuntu 18.04
CVE References
information type: | Public → Private |
Changed in linux (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Bionic): | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: bionic |
Changed in linux (Ubuntu): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in linux (Ubuntu Bionic): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
status: | Triaged → In Progress |
Changed in linux (Ubuntu): | |
status: | Triaged → In Progress |
information type: | Private → Public |
description: | updated |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
Changed in dell-poweredge: | |
status: | New → Fix Committed |
Changed in dell-poweredge: | |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu): | |
status: | Fix Committed → Fix Released |
I built a test kernel with commit 62843c2e42. The test kernel can be downloaded from: kernel. ubuntu. com/~jsalisbury /lp1797587
http://
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels: unsigned .deb packages.
• If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-
Thanks in advance!