diff options
author | Julian Wiedmann <jwi@linux.ibm.com> | 2018-05-16 09:37:25 +0200 |
---|---|---|
committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2018-06-25 10:14:37 +0200 |
commit | 64e03ff72623b8c2ea89ca3cb660094e019ed4ae (patch) | |
tree | 8fca22ca5049c83be9f8486d8474c18ce993042b /arch/s390/include/asm/qdio.h | |
parent | 891f6a726cacbb87e5b06076693ffab53bd378d7 (diff) | |
download | linux-stable-64e03ff72623b8c2ea89ca3cb660094e019ed4ae.tar.gz linux-stable-64e03ff72623b8c2ea89ca3cb660094e019ed4ae.tar.bz2 linux-stable-64e03ff72623b8c2ea89ca3cb660094e019ed4ae.zip |
s390/qdio: reset old sbal_state flags
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.
Fix this by unconditionally clearing the flags field.
Fixes: 104ea556ee7f ("qdio: support asynchronous delivery of storage blocks")
Cc: <stable@vger.kernel.org> #v3.2+
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'arch/s390/include/asm/qdio.h')
-rw-r--r-- | arch/s390/include/asm/qdio.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h index de11ecc99c7c..9c9970a5dfb1 100644 --- a/arch/s390/include/asm/qdio.h +++ b/arch/s390/include/asm/qdio.h @@ -262,7 +262,6 @@ struct qdio_outbuf_state { void *user; }; -#define QDIO_OUTBUF_STATE_FLAG_NONE 0x00 #define QDIO_OUTBUF_STATE_FLAG_PENDING 0x01 #define CHSC_AC1_INITIATE_INPUTQ 0x80 |