On Mon, 07 Oct 2024 12:24:13 -0600, Uday Shankar wrote:
> ublk currently supports the following behaviors on ublk server exit:
>
> A: outstanding I/Os get errors, subsequently issued I/Os get errors
> B: outstanding I/Os get errors, subsequently issued I/Os queue
> C: outstanding I/Os get reissued, subsequently issued I/Os queue
>
> and the following behaviors for recovery of preexisting block devices by
> a future incarnation of the ublk server:
>
> [...]
Applied, thanks!
[1/5] ublk: check recovery flags for validity
commit: 0a4f884510c68ac48d853a1d89ddb5c2f0a2db39
[2/5] ublk: refactor recovery configuration flag helpers
commit: 20f2939cbcc5a1792b71130bad626b19345a23d1
[3/5] ublk: merge stop_work and quiesce_work
commit: dbe142123bd713eeadb129f66a1357d0719ec853
[4/5] ublk: support device recovery without I/O queueing
commit: 4aef53b1cd32f61ee2bd67c764c2bf299358e740
[5/5] Documentation: ublk: document UBLK_F_USER_RECOVERY_FAIL_IO
commit: a463281eb2796a63000e0d528c1b712fdad452d0
Best regards,
--
Jens Axboe
