2018-11-27 12:49:12 |
bugproxy |
bug |
|
|
added bug |
2018-11-27 12:49:13 |
bugproxy |
tags |
|
architecture-s39064 bugnameltc-173361 severity-high targetmilestone-inin1804 |
|
2018-11-27 12:49:15 |
bugproxy |
ubuntu: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
2018-11-27 12:49:19 |
bugproxy |
affects |
ubuntu |
linux (Ubuntu) |
|
2018-11-27 12:58:51 |
Frank Heimes |
bug task added |
|
ubuntu-z-systems |
|
2018-11-27 12:59:16 |
Frank Heimes |
ubuntu-z-systems: status |
New |
Triaged |
|
2018-11-27 12:59:20 |
Frank Heimes |
ubuntu-z-systems: importance |
Undecided |
High |
|
2018-11-27 12:59:33 |
Frank Heimes |
ubuntu-z-systems: assignee |
|
Canonical Kernel Team (canonical-kernel-team) |
|
2018-11-27 13:02:42 |
Frank Heimes |
tags |
architecture-s39064 bugnameltc-173361 severity-high targetmilestone-inin1804 |
architecture-s39064 bugnameltc-173361 kernel-key severity-high targetmilestone-inin1804 |
|
2018-11-27 15:30:34 |
Joseph Salisbury |
linux (Ubuntu): status |
New |
Triaged |
|
2018-11-27 15:30:37 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
High |
|
2018-11-27 17:48:40 |
Terry Rudd |
bug |
|
|
added subscriber Terry Rudd |
2018-11-30 16:37:12 |
Joseph Salisbury |
nominated for series |
|
Ubuntu Cosmic |
|
2018-11-30 16:37:12 |
Joseph Salisbury |
bug task added |
|
linux (Ubuntu Cosmic) |
|
2018-11-30 16:37:12 |
Joseph Salisbury |
nominated for series |
|
Ubuntu Disco |
|
2018-11-30 16:37:12 |
Joseph Salisbury |
bug task added |
|
linux (Ubuntu Disco) |
|
2018-11-30 16:37:12 |
Joseph Salisbury |
nominated for series |
|
Ubuntu Bionic |
|
2018-11-30 16:37:12 |
Joseph Salisbury |
bug task added |
|
linux (Ubuntu Bionic) |
|
2018-11-30 16:37:20 |
Joseph Salisbury |
linux (Ubuntu Bionic): status |
New |
In Progress |
|
2018-11-30 16:37:24 |
Joseph Salisbury |
linux (Ubuntu Cosmic): status |
New |
In Progress |
|
2018-11-30 16:37:27 |
Joseph Salisbury |
linux (Ubuntu Disco): status |
Triaged |
In Progress |
|
2018-11-30 16:37:30 |
Joseph Salisbury |
linux (Ubuntu Cosmic): importance |
Undecided |
High |
|
2018-11-30 16:37:33 |
Joseph Salisbury |
linux (Ubuntu Bionic): importance |
Undecided |
High |
|
2018-11-30 16:37:36 |
Joseph Salisbury |
linux (Ubuntu Bionic): assignee |
|
Joseph Salisbury (jsalisbury) |
|
2018-11-30 16:37:38 |
Joseph Salisbury |
linux (Ubuntu Cosmic): assignee |
|
Joseph Salisbury (jsalisbury) |
|
2018-11-30 16:37:40 |
Joseph Salisbury |
linux (Ubuntu Disco): assignee |
Skipper Bug Screeners (skipper-screen-team) |
Joseph Salisbury (jsalisbury) |
|
2018-12-03 13:25:03 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
In Progress |
|
2018-12-14 16:49:10 |
Joseph Salisbury |
description |
Description: kernel: zcrypt: reinit ap queue state machine
Symptom: Zcrypt ap queue device not operational at host level after a
kvm guest used it.
Problem: The vfio device driver when receiving an ap queue device does
additional resets thereby removing the registration for
interrupts for the ap device done by the ap bus core
code. So when later the vfio driver releases the device and
one of the default zcrypt drivers takes care of the device
the interrupt registration needs to get renewed. The current
code does no renew and result is that requests send into such
a queue will never see a reply processed - the application
hangs.
Solution: This patch adds a function which resets the aq queue state
machine for the ap queue device and triggers the walk through
the initial states (which are reset and registration for
interrupts). This function is now called before the driver's
probe function is invoked.
When the association between driver and device is released,
the driver's remove function is called. The current
implementation calls a ap queue function
ap_queue_remove(). This invokation has been moved to the ap
bus function to make the probe / remove pair for ap bus and
drivers more symmetric.
Reproduction: Set up an kvm guest to use one or more ap queues in
pass-through mode. Start the guest. Stop the guest. Reassign
the ap resources back to the host system. Run an application
which uses exactly this ap resources. Without the fix, the
application hangs; with the fix the application should run
fine.
Upstream commit(s):
104f708fd1241b22f808bdf066ab67dc5a051de5
Available on kernel.org |
== SRU Justification ==
The vfio device driver when receiving an ap queue device does
additional resets thereby removing the registration for
interrupts for the ap device done by the ap bus core
code. So when later the vfio driver releases the device and
one of the default zcrypt drivers takes care of the device
the interrupt registration needs to get renewed. The current
code does no renew and result is that requests send into such
a queue will never see a reply processed - the application
hangs.
This commit has also been cc'd to upstream stable.
== Fix ==
104f708fd ("s390/zcrypt: reinit ap queue state machine during device probe")
== Regression Potential ==
Low. Limited to s390.
== Original Bug Description ==
Description: kernel: zcrypt: reinit ap queue state machine
Symptom: Zcrypt ap queue device not operational at host level after a
kvm guest used it.
Problem: The vfio device driver when receiving an ap queue device does
additional resets thereby removing the registration for
interrupts for the ap device done by the ap bus core
code. So when later the vfio driver releases the device and
one of the default zcrypt drivers takes care of the device
the interrupt registration needs to get renewed. The current
code does no renew and result is that requests send into such
a queue will never see a reply processed - the application
hangs.
Solution: This patch adds a function which resets the aq queue state
machine for the ap queue device and triggers the walk through
the initial states (which are reset and registration for
interrupts). This function is now called before the driver's
probe function is invoked.
When the association between driver and device is released,
the driver's remove function is called. The current
implementation calls a ap queue function
ap_queue_remove(). This invokation has been moved to the ap
bus function to make the probe / remove pair for ap bus and
drivers more symmetric.
Reproduction: Set up an kvm guest to use one or more ap queues in
pass-through mode. Start the guest. Stop the guest. Reassign
the ap resources back to the host system. Run an application
which uses exactly this ap resources. Without the fix, the
application hangs; with the fix the application should run
fine.
Upstream commit(s):
104f708fd1241b22f808bdf066ab67dc5a051de5
Available on kernel.org |
|
2018-12-20 07:42:54 |
Khaled El Mously |
linux (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
2018-12-20 07:42:57 |
Khaled El Mously |
linux (Ubuntu Cosmic): status |
In Progress |
Fix Committed |
|
2018-12-20 08:04:31 |
Frank Heimes |
ubuntu-z-systems: status |
In Progress |
Fix Committed |
|
2019-01-08 14:13:41 |
Seth Forshee |
linux (Ubuntu Disco): status |
In Progress |
Fix Committed |
|
2019-01-15 10:32:55 |
Brad Figg |
tags |
architecture-s39064 bugnameltc-173361 kernel-key severity-high targetmilestone-inin1804 |
architecture-s39064 bugnameltc-173361 kernel-key severity-high targetmilestone-inin1804 verification-needed-cosmic |
|
2019-01-15 10:37:41 |
Brad Figg |
tags |
architecture-s39064 bugnameltc-173361 kernel-key severity-high targetmilestone-inin1804 verification-needed-cosmic |
architecture-s39064 bugnameltc-173361 kernel-key severity-high targetmilestone-inin1804 verification-needed-bionic verification-needed-cosmic |
|
2019-01-17 13:20:25 |
Frank Heimes |
tags |
architecture-s39064 bugnameltc-173361 kernel-key severity-high targetmilestone-inin1804 verification-needed-bionic verification-needed-cosmic |
architecture-s39064 bugnameltc-173361 kernel-key severity-high targetmilestone-inin1804 verification-done-bionic verification-done-cosmic |
|
2019-01-17 18:01:30 |
Joseph Salisbury |
bug |
|
|
added subscriber Joseph Salisbury |
2019-01-17 18:01:59 |
Joseph Salisbury |
removed subscriber Joseph Salisbury |
|
|
|
2019-01-17 18:02:07 |
Joseph Salisbury |
bug |
|
|
added subscriber Joseph Salisbury |
2019-01-28 17:12:01 |
Launchpad Janitor |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
2019-01-28 17:12:01 |
Launchpad Janitor |
cve linked |
|
2018-14625 |
|
2019-01-28 17:12:01 |
Launchpad Janitor |
cve linked |
|
2018-16882 |
|
2019-01-28 17:12:01 |
Launchpad Janitor |
cve linked |
|
2018-17972 |
|
2019-01-28 17:12:01 |
Launchpad Janitor |
cve linked |
|
2018-18281 |
|
2019-01-28 17:12:01 |
Launchpad Janitor |
cve linked |
|
2018-19407 |
|
2019-02-04 08:48:45 |
Launchpad Janitor |
linux (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
2019-02-04 14:46:37 |
Launchpad Janitor |
linux (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
2019-02-04 16:25:20 |
Frank Heimes |
ubuntu-z-systems: status |
Fix Committed |
Fix Released |
|
2019-07-24 20:57:03 |
Brad Figg |
tags |
architecture-s39064 bugnameltc-173361 kernel-key severity-high targetmilestone-inin1804 verification-done-bionic verification-done-cosmic |
architecture-s39064 bugnameltc-173361 cscc kernel-key severity-high targetmilestone-inin1804 verification-done-bionic verification-done-cosmic |
|