> A failed PREPARE can leave subsequent START or ACK paths able to queue > requests. Device reset can also leave stale queue and pause-restart state, > and a failed open can leave period work referring to a released runtime. > > Track successful device preparation under the substream lock. Require that > state and a live virtqueue before queueing transfers. Clear preparation > before reconfiguration and reset, stop transfers before resetting the > device, detach outstanding buffers, clear queue pointers under their locks, > and cancel period work before completing state cleanup. Mark all streams > suspended so prepare re-establishes device parameters after restore. > > Keep prepared capture buffers eligible for NOMMU bounce copies during > native pause. Suppress new notifications from an inactive failed-open > path, cancel pending period work on open failure, and guard the worker > against an absent runtime. > [ ... ] > client-deadline failures on v5 and the corrected kernel; it does not > justify relaxing the capture overflow checks. > > Assisted-by: LLM > Signed-off-by: Joonho Lee <[email protected]>
Sashiko has reviewed this patch and found no issues. -- Sashiko AI review ยท https://sashiko.dev/#/patchset/[email protected]?part=13
