diff options
author | Ming Lei <ming.lei@redhat.com> | 2019-08-27 19:01:46 +0800 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2019-08-27 10:40:20 -0600 |
commit | c6ba933358f0d7a6a042b894dba20cc70396a6d3 (patch) | |
tree | e5d7c3e7fadb316f744edc706a3b8df14a4157aa /block/blk-wbt.c | |
parent | c48dac137a62a5d6fa1ef3fa445cbd9c43655a76 (diff) | |
download | linux-c6ba933358f0d7a6a042b894dba20cc70396a6d3.tar.gz linux-c6ba933358f0d7a6a042b894dba20cc70396a6d3.tar.bz2 linux-c6ba933358f0d7a6a042b894dba20cc70396a6d3.zip |
blk-mq: don't hold q->sysfs_lock in blk_mq_map_swqueue
blk_mq_map_swqueue() is called from blk_mq_init_allocated_queue()
and blk_mq_update_nr_hw_queues(). For the former caller, the kobject
isn't exposed to userspace yet. For the latter caller, hctx sysfs entries
and debugfs are un-registered before updating nr_hw_queues.
On the other hand, commit 2f8f1336a48b ("blk-mq: always free hctx after
request queue is freed") moves freeing hctx into queue's release
handler, so there won't be race with queue release path too.
So don't hold q->sysfs_lock in blk_mq_map_swqueue().
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Hannes Reinecke <hare@suse.com>
Cc: Greg KH <gregkh@linuxfoundation.org>
Cc: Mike Snitzer <snitzer@redhat.com>
Cc: Bart Van Assche <bvanassche@acm.org>
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Signed-off-by: Ming Lei <ming.lei@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk-wbt.c')
0 files changed, 0 insertions, 0 deletions