[UBUNTU] qdio: clear intparm during shutdown
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
High
|
Canonical Kernel Team | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Skipper Bug Screeners | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
SRU Justification:
[Impact]
* Crash in qeth_irq() with "Unable to handle kernel pointer dereference in virtual kernel address space"
[Fix]
* 89286320a236d24
[Test Case]
* Offline an OSA CHPID with multiple active qeth interfaces.
[Regression Potential]
* The regression potential can be considered as very low since it only affects the s390x platform
* and there it only affects the (ccW) qeth (OSA) network devices
* and again this happens if the CHPID is offlined, which usually doesn't happen during regular operation.
[Other Info]
* The patch was upstream accepted with kernel 4.17, hence it's already part of cosmic, disco and eoan and proven there to work.
* It needs to be applied to kernel 4.15 to land in 18.04 GA and 16.04.5 HWE.
_______
Description: qdio: clear intparm during shutdown
Symptom: Crash in qeth_irq() with "Unable to handle kernel pointer
Problem: During shutdown, qdio returns its ccw device back to control
by qeth - but doesn't reset the interrupt parameter on the
do so. In this case the IRQ for the IO completion is
Solution: When returning the ccw device in qdio_shutdown(), also reset
its interrupt parameter.
Reproduction: Offline an OSA CHPID with multiple active qeth interfaces.
Component: Kernel
Upstream-ID: 89286320a236d24
Reported: Ubuntu 18.04
tags: | added: architecture-s39064 bugnameltc-177513 severity-high targetmilestone-inin18041 |
Changed in ubuntu: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
Changed in ubuntu-z-systems: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in ubuntu-z-systems: | |
assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
description: | updated |
description: | updated |
Changed in linux (Ubuntu): | |
status: | New → Fix Released |
Changed in linux (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Changed in ubuntu-z-systems: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-z-systems: | |
status: | Fix Committed → Fix Released |
------- Comment From <email address hidden> 2019-05-09 07:46 EDT-------
Problem was detected on 16.04.5 but is the same kernel like 18.04.
Can a test kernel be provided for our test. That would be great......
Many thx in advance