From: Ming Lei <ming.lei@redhat.com>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: "Jens Axboe" <axboe@kernel.dk>,
linux-block@vger.kernel.org,
"Shinichiro Kawasaki" <shinichiro.kawasaki@wdc.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Christoph Hellwig" <hch@lst.de>
Subject: Re: [PATCH 15/15] block: move wbt_enable_default() out of queue freezing from scheduler's ->exit()
Date: Mon, 14 Apr 2025 09:55:04 +0800 [thread overview]
Message-ID: <Z_xq-H7eM8sD9FaU@fedora> (raw)
In-Reply-To: <d3f8673e-682f-41a2-bcae-d256e3b26746@linux.ibm.com>
On Fri, Apr 11, 2025 at 12:50:42AM +0530, Nilay Shroff wrote:
>
>
> On 4/10/25 7:00 PM, Ming Lei wrote:
> > scheduler's ->exit() is called with queue frozen and elevator lock is held, and
> > wbt_enable_default() can't be called with queue frozen, otherwise the
> > following lockdep warning is triggered:
> >
> > #6 (&q->rq_qos_mutex){+.+.}-{4:4}:
> > #5 (&eq->sysfs_lock){+.+.}-{4:4}:
> > #4 (&q->elevator_lock){+.+.}-{4:4}:
> > #3 (&q->q_usage_counter(io)#3){++++}-{0:0}:
> > #2 (fs_reclaim){+.+.}-{0:0}:
> > #1 (&sb->s_type->i_mutex_key#3){+.+.}-{4:4}:
> > #0 (&q->debugfs_mutex){+.+.}-{4:4}:
> >
> > Fix the issue by moving wbt_enable_default() out of bfq's exit(), and
> > call it from elevator_change_done().
>
> [...]
>
> > diff --git a/block/elevator.c b/block/elevator.c
> > index 1cc640a9db3e..9cf78db4d6a4 100644
> > --- a/block/elevator.c
> > +++ b/block/elevator.c
> > @@ -676,8 +676,13 @@ int elevator_change_done(struct request_queue *q, struct elev_change_ctx *ctx)
> > int ret = 0;
> >
> > if (ctx->old) {
> > + bool enable_wbt = test_bit(ELEVATOR_FLAG_ENABLE_WBT_ON_EXIT,
> > + &ctx->old->flags);
> > +
> > elv_unregister_queue(q, ctx->old);
> > kobject_put(&ctx->old->kobj);
> > + if (enable_wbt)
> > + wbt_enable_default(q->disk);
> > }
> wbt_enable_default is also called from ioc_qos_write and blk_register_queue
> with ->elevator_lock protection. So avoiding protection here doesn't seem
> correct.
The only code which needs the protection should be:
```
wbt_enable_default():
...
if (q->elevator && test_bit(ELEVATOR_FLAG_DISABLE_WBT, &q->elevator->flags))
enable = false;
```
The flag can be moved to request queue from elevator queue, will do it in
V2.
Thanks,
Ming
prev parent reply other threads:[~2025-04-14 1:55 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 13:30 [PATCH 00/15] block: unify elevator changing and fix lockdep warning Ming Lei
2025-04-10 13:30 ` [PATCH 01/15] block: don't call freeze queue in elevator_switch() and elevator_disable() Ming Lei
2025-04-10 13:30 ` [PATCH 02/15] block: add two helpers for registering/un-registering sched debugfs Ming Lei
2025-04-10 14:25 ` Christoph Hellwig
2025-04-10 13:30 ` [PATCH 03/15] block: move sched debugfs register into elvevator_register_queue Ming Lei
2025-04-10 14:27 ` Christoph Hellwig
2025-04-14 0:42 ` Ming Lei
2025-04-10 13:30 ` [PATCH 04/15] block: prevent elevator switch during updating nr_hw_queues Ming Lei
2025-04-10 14:36 ` Christoph Hellwig
2025-04-14 0:54 ` Ming Lei
2025-04-14 6:07 ` Christoph Hellwig
2025-04-15 2:03 ` Ming Lei
2025-04-11 19:13 ` Nilay Shroff
2025-04-14 0:55 ` Ming Lei
2025-04-10 13:30 ` [PATCH 05/15] block: simplify elevator reset for " Ming Lei
2025-04-10 14:40 ` Christoph Hellwig
2025-04-10 15:34 ` Christoph Hellwig
2025-04-14 0:58 ` Ming Lei
2025-04-14 6:09 ` Christoph Hellwig
2025-04-15 2:05 ` Ming Lei
2025-04-10 13:30 ` [PATCH 06/15] block: add helper of elevator_change() Ming Lei
2025-04-10 13:30 ` [PATCH 07/15] block: move blk_unregister_queue() & device_del() after freeze wait Ming Lei
2025-04-14 6:19 ` Christoph Hellwig
2025-04-15 2:26 ` Ming Lei
2025-04-10 13:30 ` [PATCH 08/15] block: add `struct elev_change_ctx` for unifying elevator change Ming Lei
2025-04-14 6:21 ` Christoph Hellwig
2025-04-10 13:30 ` [PATCH 09/15] block: " Ming Lei
2025-04-10 18:37 ` Nilay Shroff
2025-04-14 1:22 ` Ming Lei
2025-04-15 12:30 ` Nilay Shroff
2025-04-16 1:49 ` Ming Lei
2025-04-10 13:30 ` [PATCH 10/15] block: pass elevator_queue to elv_register_queue & unregister_queue Ming Lei
2025-04-14 6:22 ` Christoph Hellwig
2025-04-15 2:31 ` Ming Lei
2025-04-16 4:53 ` Christoph Hellwig
2025-04-10 13:30 ` [PATCH 11/15] block: move elv_register[unregister]_queue out of elevator_lock Ming Lei
2025-04-11 19:20 ` Nilay Shroff
2025-04-14 1:24 ` Ming Lei
2025-04-15 9:39 ` Nilay Shroff
2025-04-15 10:32 ` Ming Lei
2025-04-10 13:30 ` [PATCH 12/15] block: move debugfs/sysfs register out of freezing queue Ming Lei
2025-04-10 18:57 ` Nilay Shroff
2025-04-14 1:42 ` Ming Lei
2025-04-15 9:37 ` Nilay Shroff
2025-04-15 10:06 ` Ming Lei
2025-04-15 11:15 ` Nilay Shroff
2025-04-15 11:54 ` Ming Lei
2025-04-15 12:21 ` Nilay Shroff
2025-04-15 12:41 ` Ming Lei
2025-04-10 13:30 ` [PATCH 13/15] block: remove several ->elevator_lock Ming Lei
2025-04-10 19:07 ` Nilay Shroff
2025-04-14 1:46 ` Ming Lei
2025-04-10 13:30 ` [PATCH 14/15] block: move hctx cpuhp add/del out of queue freezing Ming Lei
2025-04-10 13:30 ` [PATCH 15/15] block: move wbt_enable_default() out of queue freezing from scheduler's ->exit() Ming Lei
2025-04-10 19:20 ` Nilay Shroff
2025-04-14 1:55 ` 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_xq-H7eM8sD9FaU@fedora \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=nilay@linux.ibm.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=thomas.hellstrom@linux.intel.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).