From: Ming Lei <ming.lei@redhat.com>
To: Uday Shankar <ushankar@purestorage.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
Caleb Sander Mateos <csander@purestorage.com>
Subject: Re: [PATCH 2/2] ublk: don't fail request for recovery & reissue in case of ubq->canceling
Date: Wed, 9 Apr 2025 09:09:45 +0800 [thread overview]
Message-ID: <Z_XI2TdYF-HV9DIO@fedora> (raw)
In-Reply-To: <Z/V0+NnMBFlPGaBX@dev-ushankar.dev.purestorage.com>
On Tue, Apr 08, 2025 at 01:11:52PM -0600, Uday Shankar wrote:
> On Tue, Apr 08, 2025 at 03:24:38PM +0800, Ming Lei wrote:
> > ubq->canceling is set with request queue quiesced when io_uring context is
> > exiting. Recovery & reissue(UBLK_F_USER_RECOVERY_REISSUE) requires
> > request to be re-queued and re-dispatch after device is recovered.
> >
> > However commit d796cea7b9f3 ("ublk: implement ->queue_rqs()") still may
> > fail any request in case of ubq->canceling, this way breaks
> > UBLK_F_USER_RECOVERY_REISSUE.
>
> This change actually affects UBLK_F_USER_RECOVERY as long as FAIL_IO
> isn't set (regardless of RECOVERY_REISSUE). RECOVERY_REISSUE only
> changes behavior for requests that are already in the ublk server when
> the ublk server dies, but the code change only affects requests that
> come in after ublk server death is already detected. At that point, both
> plain USER_RECOVERY and USER_RECOVERY|USER_RECOVERY_REISSUE should see
> requests queue instead of completing with error. See below code
> snippets:
>
> static inline void __ublk_abort_rq(struct ublk_queue *ubq,
> struct request *rq)
> {
> /* We cannot process this rq so just requeue it. */
> if (ublk_nosrv_dev_should_queue_io(ubq->dev))
> blk_mq_requeue_request(rq, false);
> else
> blk_mq_end_request(rq, BLK_STS_IOERR);
> }
>
> /*
> * Should I/O issued while there is no ublk server queue? If not, I/O
> * issued while there is no ublk server will get errors.
> */
> static inline bool ublk_nosrv_dev_should_queue_io(struct ublk_device *ub)
> {
> return (ub->dev_info.flags & UBLK_F_USER_RECOVERY) &&
> !(ub->dev_info.flags & UBLK_F_USER_RECOVERY_FAIL_IO);
> }
Indeed, will update commit log.
>
> >
> > Fix it by calling __ublk_abort_rq() in case of ubq->canceling.
> >
> > Reported-by: Uday Shankar <ushankar@purestorage.com>
> > Closes: https://lore.kernel.org/linux-block/Z%2FQkkTRHfRxtN%2FmB@dev-ushankar.dev.purestorage.com/
> > Fixes: commit d796cea7b9f3 ("ublk: implement ->queue_rqs()")
>
> Will this upset anything parsing these tags? The syntax I've usually
> seen doesn't have "commit," i.e.
>
> Fixes: d796cea7b9f3 ("ublk: implement ->queue_rqs()")
Will fix it in V2.
Thanks
Ming
prev parent reply other threads:[~2025-04-09 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 7:24 [PATCH 0/2] ublk: two fixes Ming Lei
2025-04-08 7:24 ` [PATCH 1/2] ublk: fix handling recovery & reissue in ublk_abort_queue() Ming Lei
2025-04-09 1:47 ` Caleb Sander Mateos
2025-04-09 3:17 ` Ming Lei
2025-04-09 15:47 ` Caleb Sander Mateos
2025-04-08 7:24 ` [PATCH 2/2] ublk: don't fail request for recovery & reissue in case of ubq->canceling Ming Lei
2025-04-08 19:11 ` Uday Shankar
2025-04-09 1:09 ` Ming Lei [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=Z_XI2TdYF-HV9DIO@fedora \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=linux-block@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).