c3f62bf34a
Detecting for internal recovery and flush execute in two different thread contexts, and the critical section protecting the lists is small to avoid locking overhead. It is possible that flush was triggered, but bh in ISP detected an error condition and triggers a internal recovery moving the request in question to pending list. At this point it is possible, that the flush context has cleared the pending list, and internal recovery's addition to the pending list is agnostic to the flushing thread. When there is a flush all, a reset is issued to the HW and all the bh's are flushed as well. Post this clearing the pending request list ensures no stale request entity is left behind as opposed to cleaning up the pending list prior to the HW stop sequence. CRs-Fixed: 3669530 Change-Id: I58f024ec51cbc9c391d8aab1199098f314317b8a Signed-off-by: Karthik Anantha Ram <quic_kartanan@quicinc.com> (cherry picked from commit 0d58af6cf25db3b3412bc6effc437474751bf700)