Linux block layer
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Omar Sandoval <osandov@fb.com>,
	Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCH v3 1/8] blk-mq: Register <dev>/queue/mq after having registered <dev>/queue
Date: Fri, 21 Apr 2017 15:05:18 -0700	[thread overview]
Message-ID: <20170421220518.GA17177@vader.DHCP.thefacebook.com> (raw)
In-Reply-To: <20170418232949.5228-2-bart.vanassche@sandisk.com>

On Tue, Apr 18, 2017 at 04:29:42PM -0700, Bart Van Assche wrote:
> A later patch in this series will modify blk_mq_debugfs_register()
> such that it uses q->kobj.parent to determine the name of a
> request queue. Hence make sure that that pointer is initialized
> before blk_mq_debugfs_register() is called. To avoid lock inversion,
> protect sysfs / debugfs registration with the queue sysfs_lock
> instead of the global mutex all_q_mutex.

I think this is sane, I don't see why we would need all_q_mutex for
this. One comment below, however.

> Signed-off-by: Bart Van Assche <bart.vanassche@sandisk.com>
> Cc: Omar Sandoval <osandov@fb.com>
> Cc: Hannes Reinecke <hare@suse.com>
> ---
>  block/blk-mq-sysfs.c | 43 +++++++++++++++++++++++++++++++++++--------
>  block/blk-mq.h       |  1 +
>  block/blk-sysfs.c    |  6 +++---
>  3 files changed, 39 insertions(+), 11 deletions(-)
> 
> diff --git a/block/blk-mq-sysfs.c b/block/blk-mq-sysfs.c
> index d745ab81033a..54ef9402914c 100644
> --- a/block/blk-mq-sysfs.c
> +++ b/block/blk-mq-sysfs.c
> @@ -253,6 +253,8 @@ static void __blk_mq_unregister_dev(struct device *dev, struct request_queue *q)
>  	struct blk_mq_hw_ctx *hctx;
>  	int i;
>  
> +	lockdep_assert_held(&q->sysfs_lock);
> +
>  	queue_for_each_hw_ctx(q, hctx, i)
>  		blk_mq_unregister_hctx(hctx);
>  
> @@ -267,9 +269,9 @@ static void __blk_mq_unregister_dev(struct device *dev, struct request_queue *q)
>  
>  void blk_mq_unregister_dev(struct device *dev, struct request_queue *q)
>  {
> -	blk_mq_disable_hotplug();
> +	mutex_lock(&q->sysfs_lock);
>  	__blk_mq_unregister_dev(dev, q);
> -	blk_mq_enable_hotplug();
> +	mutex_unlock(&q->sysfs_lock);
>  }
>  
>  void blk_mq_hctx_kobj_init(struct blk_mq_hw_ctx *hctx)
> @@ -302,12 +304,13 @@ void blk_mq_sysfs_init(struct request_queue *q)
>  	}
>  }
>  
> -int blk_mq_register_dev(struct device *dev, struct request_queue *q)
> +int __blk_mq_register_dev(struct device *dev, struct request_queue *q)
>  {
>  	struct blk_mq_hw_ctx *hctx;
>  	int ret, i;
>  
> -	blk_mq_disable_hotplug();
> +	WARN_ON_ONCE(!q->kobj.parent);
> +	lockdep_assert_held(&q->sysfs_lock);
>  
>  	ret = kobject_add(&q->mq_kobj, kobject_get(&dev->kobj), "%s", "mq");
>  	if (ret < 0)
> @@ -327,8 +330,20 @@ int blk_mq_register_dev(struct device *dev, struct request_queue *q)
>  		__blk_mq_unregister_dev(dev, q);
>  	else
>  		q->mq_sysfs_init_done = true;
> +
>  out:
> -	blk_mq_enable_hotplug();
> +	return ret;
> +}
> +
> +int blk_mq_register_dev(struct device *dev, struct request_queue *q)
> +{
> +	int ret;
> +
> +	ret = mutex_lock_interruptible(&q->sysfs_lock);

Why did you make this interruptible? blk_mq_disable_hotplug() wasn't
interruptible before, so now dm_mq_init_request_queue() can fail
silently if it is interrupted.

  reply	other threads:[~2017-04-21 22:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 23:29 [PATCH v3 0/8] blk-mq debugfs patches for kernel v4.12 Bart Van Assche
2017-04-18 23:29 ` [PATCH v3 1/8] blk-mq: Register <dev>/queue/mq after having registered <dev>/queue Bart Van Assche
2017-04-21 22:05   ` Omar Sandoval [this message]
2017-04-21 22:09     ` Bart Van Assche
2017-04-21 22:11       ` Omar Sandoval
2017-04-18 23:29 ` [PATCH v3 2/8] blk-mq: Let blk_mq_debugfs_register() look up the queue name Bart Van Assche
2017-04-21 22:06   ` Omar Sandoval
2017-04-18 23:29 ` [PATCH v3 3/8] blk-mq: Unregister debugfs attributes earlier Bart Van Assche
2017-04-21 22:16   ` Omar Sandoval
2017-04-21 22:17     ` Omar Sandoval
2017-04-18 23:29 ` [PATCH v3 4/8] blk-mq: Move the "state" debugfs attribute one level down Bart Van Assche
2017-04-18 23:29 ` [PATCH v3 5/8] blk-mq: Make blk_flags_show() callers append a newline character Bart Van Assche
2017-04-18 23:29 ` [PATCH v3 6/8] blk-mq: Show operation, cmd_flags and rq_flags names Bart Van Assche
2017-04-18 23:29 ` [PATCH v3 7/8] blk-mq: Add blk_mq_ops.show_rq() Bart Van Assche
2017-04-20 20:49   ` Omar Sandoval
2017-04-18 23:29 ` [PATCH v3 8/8] scsi: Implement blk_mq_ops.show_rq() Bart Van Assche
2017-04-19 23:25   ` Martin K. Petersen
2017-04-19 23:29     ` Bart Van Assche

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=20170421220518.GA17177@vader.DHCP.thefacebook.com \
    --to=osandov@osandov.com \
    --cc=axboe@kernel.dk \
    --cc=bart.vanassche@sandisk.com \
    --cc=hare@suse.com \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@fb.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