| 2018-11-05 08:59:44 |
bugproxy |
bug |
|
|
added bug |
| 2018-11-05 08:59:47 |
bugproxy |
tags |
|
architecture-s39064 bugnameltc-172877 severity-high targetmilestone-inin--- |
|
| 2018-11-05 08:59:48 |
bugproxy |
ubuntu: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
| 2018-11-05 08:59:50 |
bugproxy |
affects |
ubuntu |
linux (Ubuntu) |
|
| 2018-11-05 09:35:44 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Disco |
|
| 2018-11-05 09:35:44 |
Dimitri John Ledkov |
bug task added |
|
linux (Ubuntu Disco) |
|
| 2018-11-05 09:35:44 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Xenial |
|
| 2018-11-05 09:35:44 |
Dimitri John Ledkov |
bug task added |
|
linux (Ubuntu Xenial) |
|
| 2018-11-05 09:35:44 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Cosmic |
|
| 2018-11-05 09:35:44 |
Dimitri John Ledkov |
bug task added |
|
linux (Ubuntu Cosmic) |
|
| 2018-11-05 09:35:44 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-11-05 09:35:44 |
Dimitri John Ledkov |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2018-11-05 09:36:06 |
Dimitri John Ledkov |
linux (Ubuntu Disco): assignee |
Skipper Bug Screeners (skipper-screen-team) |
Canonical Kernel (canonical-kernel) |
|
| 2018-11-05 09:48:23 |
Frank Heimes |
bug task added |
|
ubuntu-z-systems |
|
| 2018-11-05 09:54:07 |
Frank Heimes |
ubuntu-z-systems: assignee |
|
Canonical Kernel Team (canonical-kernel-team) |
|
| 2018-11-05 18:19:25 |
Frank Heimes |
description |
Description: qdio: reset old sbal_state flags
Symptom: af_iucv socket using HiperSockets may stall.
Problem: When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution: Unconditionally clear the buffer's flags field.
Reproduction: Error inject, simulating out-of-memory.
kernel 4.20
Upstream-ID: 64e03ff72623b8c2ea89ca3cb660094e019ed4ae
Canonical , please provide this fix for all Releases in Service....
Ubuntu 18.10, 18.04 and 16.04 |
== SRU Justification ==
Description: qdio: reset old sbal_state flags
Symptom:
af_iucv socket using HiperSockets may stall.
Problem:
When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution:
Unconditionally clear the buffer's flags field.
== Fix ==
64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old sbal_state flags")
== Regression Potential ==
Low, because:
- s390x only
- further limited to qeth driver (OSA Express networking)
- changes are limited to two files and 6 lines
- arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
- drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
- changes are upstream in 4.20 (according to bug description,
but in 4.19 according to 'git tag'),
hence will make it automatically into 'disco'
- error was identified at IBM/customer, fix was created there and tested upfront
== Test Case ==
Test case / reproduction:
Error inject and then simulate out-of-memory situation.
__________
Description: qdio: reset old sbal_state flags
Symptom: af_iucv socket using HiperSockets may stall.
Problem: When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution: Unconditionally clear the buffer's flags field.
Reproduction: Error inject, simulating out-of-memory.
kernel 4.20
Upstream-ID: 64e03ff72623b8c2ea89ca3cb660094e019ed4ae
Canonical , please provide this fix for all Releases in Service....
Ubuntu 18.10, 18.04 and 16.04 |
|
| 2018-11-05 18:20:04 |
Frank Heimes |
description |
== SRU Justification ==
Description: qdio: reset old sbal_state flags
Symptom:
af_iucv socket using HiperSockets may stall.
Problem:
When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution:
Unconditionally clear the buffer's flags field.
== Fix ==
64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old sbal_state flags")
== Regression Potential ==
Low, because:
- s390x only
- further limited to qeth driver (OSA Express networking)
- changes are limited to two files and 6 lines
- arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
- drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
- changes are upstream in 4.20 (according to bug description,
but in 4.19 according to 'git tag'),
hence will make it automatically into 'disco'
- error was identified at IBM/customer, fix was created there and tested upfront
== Test Case ==
Test case / reproduction:
Error inject and then simulate out-of-memory situation.
__________
Description: qdio: reset old sbal_state flags
Symptom: af_iucv socket using HiperSockets may stall.
Problem: When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution: Unconditionally clear the buffer's flags field.
Reproduction: Error inject, simulating out-of-memory.
kernel 4.20
Upstream-ID: 64e03ff72623b8c2ea89ca3cb660094e019ed4ae
Canonical , please provide this fix for all Releases in Service....
Ubuntu 18.10, 18.04 and 16.04 |
== SRU Justification ==
Description: qdio: reset old sbal_state flags
Symptom:
af_iucv socket using HiperSockets may stall.
Problem:
When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution:
Unconditionally clear the buffer's flags field.
== Fix ==
64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old sbal_state flags")
== Regression Potential ==
Low, because:
- s390x only
- further limited to qeth driver (OSA Express networking)
- changes are limited to two files and 6 lines
- arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
- drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
- error was identified at IBM/customer, fix was created there and tested upfront
- (changes are upstream in 4.20 (according to bug description,
but in 4.19 according to 'git tag'),
hence will make it automatically into 'disco')
== Test Case ==
Test case / reproduction:
Error inject and then simulate out-of-memory situation.
__________
Description: qdio: reset old sbal_state flags
Symptom: af_iucv socket using HiperSockets may stall.
Problem: When allocating a new AOB fails, handle_outbound() is
still capable of transmitting the selected buffer
(just without async completion).
But if a previous transfer on this queue slot used
async completion, its sbal_state flags field is still set
to QDIO_OUTBUF_STATE_FLAG_PENDING.
So when the upper layer driver sees this stale flag, it
expects an async completion that never happens.
Solution: Unconditionally clear the buffer's flags field.
Reproduction: Error inject, simulating out-of-memory.
kernel 4.20
Upstream-ID: 64e03ff72623b8c2ea89ca3cb660094e019ed4ae
Canonical , please provide this fix for all Releases in Service....
Ubuntu 18.10, 18.04 and 16.04 |
|
| 2018-11-06 17:13:42 |
Frank Heimes |
ubuntu-z-systems: importance |
Undecided |
High |
|
| 2018-11-06 17:13:46 |
Frank Heimes |
ubuntu-z-systems: status |
New |
Triaged |
|
| 2018-11-08 04:23:08 |
Khaled El Mously |
linux (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2018-11-08 04:24:08 |
Khaled El Mously |
linux (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2018-11-08 04:24:14 |
Khaled El Mously |
linux (Ubuntu Cosmic): status |
New |
Fix Committed |
|
| 2018-11-08 06:15:27 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
Fix Committed |
|
| 2018-11-08 11:07:48 |
Stefan Bader |
linux (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2018-11-08 11:07:59 |
Stefan Bader |
linux (Ubuntu Disco): status |
New |
Fix Released |
|
| 2018-11-08 11:10:40 |
Stefan Bader |
linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2018-11-15 11:34:39 |
Brad Figg |
tags |
architecture-s39064 bugnameltc-172877 severity-high targetmilestone-inin--- |
architecture-s39064 bugnameltc-172877 severity-high targetmilestone-inin--- verification-needed-bionic |
|
| 2018-11-22 09:21:25 |
Frank Heimes |
tags |
architecture-s39064 bugnameltc-172877 severity-high targetmilestone-inin--- verification-needed-bionic |
architecture-s39064 bugnameltc-172877 severity-high targetmilestone-inin--- verification-done-bionic |
|
| 2018-11-22 12:19:27 |
bugproxy |
tags |
architecture-s39064 bugnameltc-172877 severity-high targetmilestone-inin--- verification-done-bionic |
architecture-s39064 bugnameltc-172877 severity-high targetmilestone-inin1810 verification-done-bionic |
|
| 2018-12-03 14:01:15 |
Launchpad Janitor |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-12-03 14:01:15 |
Launchpad Janitor |
cve linked |
|
2018-18955 |
|
| 2018-12-03 14:28:36 |
Frank Heimes |
ubuntu-z-systems: status |
Fix Committed |
Fix Released |
|
| 2019-07-24 21:29:33 |
Brad Figg |
tags |
architecture-s39064 bugnameltc-172877 severity-high targetmilestone-inin1810 verification-done-bionic |
architecture-s39064 bugnameltc-172877 cscc severity-high targetmilestone-inin1810 verification-done-bionic |
|
