NVMe timeout is too short
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Daniel Axtens | ||
Trusty |
Fix Released
|
Medium
|
Daniel Axtens | ||
Xenial |
Fix Released
|
Medium
|
Unassigned | ||
Zesty |
Fix Released
|
Medium
|
Unassigned | ||
Artful |
Fix Released
|
Medium
|
Unassigned | ||
linux-aws (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Zesty |
Invalid
|
Undecided
|
Unassigned | ||
Artful |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[SRU Justification]
[Impact]
Some NVMe operations time out too quickly. The module parameters allow the timeouts to be extended, but only up to 255s, as the counters are bytes.
[Fix]
The underlying parameters are unsigned ints, so make the module parameters unsigned ints too, by picking patch http://
(Trusty specific) This also requires picking the patch that converts
the constant into a parameter, which is a clean cherry-pick.
[Regression Potential]
(X/Z/A) Very limited: only types of module parameters are changing, the patch is easily reviewable.
(Trusty specific) Limited: a module parameter is added and its type is
changed. The patches are easily reviewable.
[Testing]
(Trusty only) Boot tested on a c5.large instance on AWS which uses
NVMe to boot. Verified that the system still boots with the patches,
and that a timeout of 123456s is permitted.
CVE References
Changed in linux-aws (Ubuntu): | |
status: | New → Confirmed |
Changed in linux-aws (Ubuntu Xenial): | |
status: | New → Fix Committed |
tags: |
added: verification-done-xenial removed: verification-needed-xenial |
Changed in linux-aws (Ubuntu Zesty): | |
status: | New → Invalid |
Changed in linux-aws (Ubuntu Artful): | |
status: | New → Invalid |
Changed in linux (Ubuntu Artful): | |
importance: | Undecided → Medium |
status: | New → Fix Committed |
Changed in linux (Ubuntu Zesty): | |
importance: | Undecided → Medium |
status: | New → Fix Committed |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → Medium |
status: | New → Fix Committed |
description: | updated |
Changed in linux (Ubuntu Trusty): | |
status: | In Progress → Fix Committed |
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 'verification- needed- xenial' to 'verification- failed- xenial' .
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!