linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Bart Van Assche <bvanassche@acm.org>,
	Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	linux-block@vger.kernel.org
Subject: Re: [blktests] zbd/012: Test requeuing of zoned writes and queue freezing
Date: Wed, 27 Nov 2024 00:58:16 -0800	[thread overview]
Message-ID: <Z0bfKNMKhLkEHusz@infradead.org> (raw)
In-Reply-To: <0e2dc18f-d84e-4dcf-a5c2-134d579c480c@kernel.org>

On Wed, Nov 27, 2024 at 05:17:08PM +0900, Damien Le Moal wrote:
> After all these fixes, the last remaining problem is the zone write
> plug error recovery issuing a report zone which can block if a queue 
> freeze was initiated.
>
> That can prevent forward progress and hang the freeze caller. I do not
> see any way to avoid that report zones. I think this could be fixed with
> a magic BLK_MQ_REQ_INTERNAL flag passed to blk_mq_alloc_request() and
> propagated to blk_queue_enter() to forcefully take a queue usage counter
> reference even if a queue freeze was started. That would ensure forward
> progress (i.e. scsi_execute_cmd() or the NVMe equivalent would not block
> forever). Need to think more about that.

You are talking about disk_zone_wplug_handle_error here, right?

We should not issue a report zones to a frozen queue, as that would
bypass the freezing protection.  I suspect the right thing is to
simply defer the error recovery action until after the queue is
unfrozen.

I wonder if the separate error work handler should go away, instead
blk_zone_wplug_bio_work should always check for an error first
and in that case do the report zones.  And blk_zone_wplug_handle_write
would always defer to the work queue if there was an error.


  reply	other threads:[~2024-11-27  8:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 21:10 [blktests] zbd/012: Test requeuing of zoned writes and queue freezing Bart Van Assche
2024-11-26  8:34 ` Damien Le Moal
2024-11-26 13:44   ` Bart Van Assche
2024-11-27  5:18     ` Damien Le Moal
2024-11-27  6:16       ` Christoph Hellwig
2024-11-27  6:21         ` Christoph Hellwig
2024-11-27  6:32           ` Damien Le Moal
2024-11-27  6:33             ` Christoph Hellwig
2024-11-27  6:43               ` Damien Le Moal
2024-11-27  6:45                 ` Christoph Hellwig
2024-11-27  7:02                   ` Damien Le Moal
2024-11-27  7:19                     ` Christoph Hellwig
2024-11-27  8:17                       ` Damien Le Moal
2024-11-27  8:58                         ` Christoph Hellwig [this message]
2024-11-27 11:31                           ` Damien Le Moal
2024-11-27 16:58                             ` Christoph Hellwig
2024-11-27 23:18                               ` Damien Le Moal
2024-11-27 23:36                                 ` Bart Van Assche
2024-11-27 23:43                                   ` Damien Le Moal
2024-11-28  3:20                                 ` Christoph Hellwig
2024-11-28  4:37                                   ` Damien Le Moal
2024-11-28  4:39                                     ` Christoph Hellwig
2024-11-28  4:52                                       ` Damien Le Moal
2024-11-28  5:00                                         ` Christoph Hellwig
2024-11-28  5:07                                           ` Damien Le Moal
2024-11-28  5:16                                             ` Christoph Hellwig
2024-11-28  5:19                                               ` Damien Le Moal
2024-11-28  5:21                                                 ` Christoph Hellwig
2024-11-28  5:27                                                   ` Damien Le Moal
2024-11-27 17:10           ` Bart Van Assche
2024-11-27 23:11             ` Damien Le Moal
2024-11-26 11:26 ` Damien Le Moal
2024-11-26 12:49   ` Christoph Hellwig
2024-11-27  2:28     ` Damien Le Moal
2024-11-28  4:35 ` Shinichiro Kawasaki

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=Z0bfKNMKhLkEHusz@infradead.org \
    --to=hch@infradead.org \
    --cc=bvanassche@acm.org \
    --cc=dlemoal@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.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).