qdio: don't retry EQBS after CCQ 96

[bugproxy]

Description: qdio: don't retry EQBS after CCQ 96

Symptom: Queue stalls, over-/underreporting of buffer errors.

Problem: Immediate retry of EQBS after CCQ 96 means that we
              potentially misreport the state of buffers inspected
              during the first EQBS call.

Solution: On CCQ 96, first process the discovered state.
              Afterwards, higher-level code will eventually trigger an
              EQBS/inspection of the remaining buffers. Their state is
              now processed independently from the state that was
              discovered during the first EQBS.

Upstream-ID: dae55b6fef58530c13df074bcc182c096609339e

[Frank Heimes (fheimes)]

Is this bionic only or does this also affect other Ubuntu releases?

[Joseph Salisbury (jsalisbury)]

Per the commit message for commit dae55b6fef5, the requested patch is also needed in Trusty and Xenial:

Fixes: 25f269f17316 ("[S390] qdio: EQBS retry after CCQ 96")
Cc: <email address hidden> #v3.2+

[Joseph Salisbury (jsalisbury)]

The requested commit is in Bionic as of Ubuntu-4.15.0-23.25~80:
25dbc82 s390/qdio: don't retry EQBS after CCQ 96

The requested commit is in Xenial as of Ubuntu-4.4.0-128.154~221:
e26f413 s390/qdio: don't retry EQBS after CCQ 96

[Frank Heimes (fheimes)]

Since dae55b6 is tagged with v4.17-rc1~78^2~13 and we have 4.17 in cosmic proposed, I change 'linux (Ubuntu)' to Fix Committed.

[Dimitri John Ledkov (xnox)]

$ git tag --contains dae55b6 Ubuntu-4.17.0-6.7
Ubuntu-4.17.0-6.7

And released.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2018-08-06 06:05 EDT-------
IBM Bugzilla status -> closed, Fix Released with Xenial and Bionic