On Fri, 30 Oct 2020 10:07:11 -0700 Sukadev Bhattiprolu wrote: > Commit 5a18e1e0c193b introduced the 'failover_pending' state to track > the "failover pending window" - where we wait for the partner to become > ready (after a transport event) before actually attempting to failover. > i.e window is between following two events: > > a. we get a transport event due to a FAILOVER > > b. later, we get CRQ_INITIALIZED indicating the partner is > ready at which point we schedule a FAILOVER reset. > > and ->failover_pending is true during this window. > > If during this window, we attempt to open (or close) a device, we pretend > that the operation succeded and let the FAILOVER reset path complete the > operation.
Applied, thanks!
