linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, shinichiro.kawasaki@wdc.com,
	dan.j.williams@intel.com, yukuai3@huawei.com,
	linux-block@vger.kernel.org
Subject: Re: [PATCH] block: remove per-disk debugfs files in blk_unregister_queue
Date: Tue, 24 May 2022 20:14:18 +0800	[thread overview]
Message-ID: <YozMGvN/3TJirE3N@T590> (raw)
In-Reply-To: <20220524120134.GB17563@lst.de>

On Tue, May 24, 2022 at 02:01:34PM +0200, Christoph Hellwig wrote:
> On Tue, May 24, 2022 at 07:47:03PM +0800, Ming Lei wrote:
> > Not look into details yet, but as one blk-mq debugfs user, I don't like
> > the idea, since I often see io hang issue when calling
> > blk_mq_freeze_queue_wait(), and blk-mq debugfs is very helpful for
> > investigating this kind of issue.
> > 
> > But now blk-mq debugfs is gone with this patch __before__ draining IO in
> > del_gendisk, and it becomes not useful as before.
> 
> This is the way hot it is set up, so in doubt I want it to be torn down
> synchronously.  There might be a way to move the teardown later, but
> that will require a very careful audit.

Then please move it to disk release at least, when blk-mq debug becomes
less useful.

In theory, blk_cleanup_queue() may have similar issue, but most of
drivers release disk after blk_cleanup_queue() except for scsi disk.

So from user viewpoint, the best place to tear down blk-mq debugfs is
still in queue release handler.

Thanks,
Ming


  reply	other threads:[~2022-05-24 12:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  8:33 [PATCH] block: remove per-disk debugfs files in blk_unregister_queue Christoph Hellwig
2022-05-24  9:29 ` Hannes Reinecke
2022-05-24 12:00   ` Christoph Hellwig
2022-05-24 11:47 ` Ming Lei
2022-05-24 12:01   ` Christoph Hellwig
2022-05-24 12:14     ` Ming Lei [this message]
2022-05-24 13:06       ` Christoph Hellwig
2022-05-24 14:44 ` Ming Lei
2022-05-27  7:15   ` Christoph Hellwig

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=YozMGvN/3TJirE3N@T590 \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dan.j.williams@intel.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=yukuai3@huawei.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).