linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Ming Lei <ming.lei@redhat.com>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Hannes Reinecke <hare@suse.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	Mike Snitzer <snitzer@redhat.com>
Subject: Re: [PATCH] block: don't release queue's sysfs lock during switching elevator
Date: Tue, 24 Sep 2019 11:37:09 -0700	[thread overview]
Message-ID: <bc5864cd-a62b-d6d5-2d69-6ec03983508b@acm.org> (raw)
In-Reply-To: <20190923151209.7466-1-ming.lei@redhat.com>

On 9/23/19 8:12 AM, Ming Lei wrote:
> @@ -523,11 +521,9 @@ void elv_unregister_queue(struct request_queue *q)
>   		kobject_uevent(&e->kobj, KOBJ_REMOVE);
>   		kobject_del(&e->kobj);
>   
> -		mutex_lock(&q->sysfs_lock);
>   		e->registered = 0;
>   		/* Re-enable throttling in case elevator disabled it */
>   		wbt_enable_default(q);
> -		mutex_unlock(&q->sysfs_lock);
>   	}
>   }

Does this patch cause sysfs_lock to be held around 
kobject_del(&e->kobj)? Since sysfs_lock is locked from inside 
elv_attr_show() and elv_attr_store(), does this mean that this patch 
reintroduces the lock inversion problem that was fixed recently?

Thanks,

Bart.

  reply	other threads:[~2019-09-24 18:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23 15:12 [PATCH] block: don't release queue's sysfs lock during switching elevator Ming Lei
2019-09-24 18:37 ` Bart Van Assche [this message]
2019-09-25  0:13   ` Ming Lei
2019-09-25 23:40     ` Bart Van Assche
2019-09-26  6:46 ` Jens Axboe

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=bc5864cd-a62b-d6d5-2d69-6ec03983508b@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=gregkh@linuxfoundation.org \
    --cc=hare@suse.com \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=snitzer@redhat.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).