Re: [PATCH] ublk: dispatch the next fetch after a batch failure
From: Jens Axboe
Date: Sun Nov 15 2026 - 10:43:06 EST
On Sun, 15 Nov 2026 00:33:52 +0800, shao.mingyin@xxxxxxxxxx wrote:
> When a batch fetch fails, for example because its provided-buffer group
> is empty, ublk_batch_dispatch() removes the failed fetch and returns.
> Pending I/O tags stay in evts_fifo even if another fetch with usable
> buffers is already queued. With no new I/O or fetch submission to select
> it, that fetch and the outstanding block requests cannot make progress.
>
> Claim the next queued fetch under evts_lock before completing and freeing
> the failed one, then schedule its dispatch in the proper task context.
> Marking it active before dropping the lock also prevents cancellation
> from taking it before its task work is queued.
>
> [...]
Applied, thanks!
[1/1] ublk: dispatch the next fetch after a batch failure
commit: a6f37fb3f5747bb7cca5cd6630dfeea4435022a1
Best regards,
--
Jens Axboe