s390/cio: fix reset of channel measurement block
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
High
|
Tim Gardner | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Tim Gardner | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
== Comment: #0 - Hendrik Brueckner <email address hidden> - 2016-08-03 09:04:43 ==
Please backport:
commit 0f5d050ceaa31b2
Author: Sebastian Ott <email address hidden>
Date: Tue Jul 12 19:57:57 2016 +0200
s390/cio: allow to reset channel measurement block
Prior to commit 1bc6664bdfb949b
enable_cmf for a device for which channel measurement was already
enabled resulted in a reset of the measurement data.
What looked like bugs at the time (a 2nd allocation was triggered
but failed, reset was called regardless of previous failures, and
errors have not been reported to userspace) was actually something
at least one userspace tool depended on. Restore that behavior in
a sane way.
Fixes: 1bc6664bdfb ("s390/cio: use device_lock during cmb activation")
Cc: <email address hidden> #v4.4+
Signed-off-by: Sebastian Ott <email address hidden>
Reviewed-by: Cornelia Huck <email address hidden>
Reviewed-by: Peter Oberparleiter <email address hidden>
Signed-off-by: Martin Schwidefsky <email address hidden>
tags: | added: architecture-s39064 bugnameltc-144469 severity-high targetmilestone-inin1604 |
Changed in ubuntu: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
Changed in ubuntu-z-systems: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Tim Gardner (timg-tpi) |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
tags: | removed: bugnameltc-144469 severity-high |
Changed in ubuntu-z-systems: | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-xenial removed: verification-needed-xenial |
Changed in ubuntu-z-systems: | |
status: | Fix Committed → Fix Released |
commit 0f5d050ceaa31b2 229102211d60c14 9f920df3aa was merged in 4.8