Re: [PATCH rtw-next v2 3/4] wifi: rtl8xxxu: preserve RX requests across recoverable transfer errors

[‍김우석[학생](전자정보대학 전자공학과)]

Hi Ping-Ke,

Thanks for the review.

Yes, the additional delay is part of the reason for the separate retry
path. For v3, I'll merge the common queueing code into one helper with a
retry flag, so the locking, shutdown check and list insertion are shared.

I'd like to keep the retry list and delayed work separate from normal
pending requests, though. Putting failed requests directly on the normal
pending list can let normal completions bypass the error backoff, while
delaying the shared submission work can also delay replenishment of
normal RX requests. Keeping the two lists preserves the existing normal
RX scheduling while removing the duplicated queueing code.

For the Fixes tag, the issue is that a finite burst of completion errors
can shrink the RX URB pool until the remaining requests no longer reach
the resubmission threshold. RX can then remain stopped even after the
errors have ended. I'll make that failure mode more explicit in the
commit message and validate the revised path with fault injection for v3.

Thanks,
Wooseok