[PATCH] nvme: reset delayed remve_work after reconnect
Nilay Shroff
nilay at linux.ibm.com
Tue Jun 10 21:21:18 PDT 2025
On 6/10/25 12:18 AM, Keith Busch wrote:
> From: Keith Busch <kbusch at kernel.org>
>
>
> The remove_work will proceed with permanently disconnecting on the
> initial final path failure if the head shows no paths after the delay.
> If a new path connects while the remove_work is pending, and if that new
> path happens to disconnect before that remove_work executes, the delayed
> removal should reset based on the most recent path disconnect time, but
> queue_delayed_work() won't do anything if the work is already pending.
> Attempt to cancel the delayed work when a new path connects, and use
> mod_delayed_work() in case the remove_work remains pending anyway.
>
> Signed-off-by: Keith Busch <kbusch at kernel.org>
Looks good to me:
Reviewed-by: Nilay Shroff <nilay at linux.ibm.com>
More information about the Linux-nvme
mailing list