From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
Uday Shankar <ushankar@purestorage.com>
Cc: linux-block@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v4 0/5] ublk: support device recovery without I/O queueing
Date: Tue, 08 Oct 2024 09:07:55 -0600 [thread overview]
Message-ID: <172840007574.12645.10207244713759182674.b4-ty@kernel.dk> (raw)
In-Reply-To: <20241007182419.3263186-1-ushankar@purestorage.com>
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
prev parent reply other threads:[~2024-10-08 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 18:24 [PATCH v4 0/5] ublk: support device recovery without I/O queueing Uday Shankar
2024-10-07 18:24 ` [PATCH v4 1/5] ublk: check recovery flags for validity Uday Shankar
2024-10-07 18:24 ` [PATCH v4 2/5] ublk: refactor recovery configuration flag helpers Uday Shankar
2024-10-07 18:24 ` [PATCH v4 3/5] ublk: merge stop_work and quiesce_work Uday Shankar
2024-10-07 18:24 ` [PATCH v4 4/5] ublk: support device recovery without I/O queueing Uday Shankar
2024-10-08 2:48 ` Ming Lei
2024-10-07 18:24 ` [PATCH v4 5/5] Documentation: ublk: document UBLK_F_USER_RECOVERY_FAIL_IO Uday Shankar
2024-10-08 2:49 ` Ming Lei
2024-10-08 15:07 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=172840007574.12645.10207244713759182674.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=ushankar@purestorage.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox