On Thu, Jun 26, 2025 at 06:29:09AM +0000, Parav Pandit wrote:

quoted

quoted

quoted

yes however this is not at all different that hotunplug right after reset.

For hotunplug after reset, we likely need a timeout handler.
Because block driver running inside the remove() callback waiting for the IO,

may not get notified from driver core to synchronize ongoing remove().


Notified of what? 

Notification that surprise-removal occurred.

quoted

So is the scenario that graceful remove starts, and
meanwhile a surprise removal happens?

Right.

where is it stuck then? can you explain?