diff options
author | Christoph Hellwig <hch@lst.de> | 2022-07-20 15:05:41 +0200 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2022-07-21 10:59:02 -0600 |
commit | c5db2cfc6274692d821d33b59acb6ff615e350c1 (patch) | |
tree | 1f9c99668b9be71dd61a60e02228e60ec1351e24 /block/bdev.c | |
parent | 0a3e5cc7bbfcd571a2e53779ef7d7aa3c57d5432 (diff) | |
download | linux-c5db2cfc6274692d821d33b59acb6ff615e350c1.tar.gz linux-c5db2cfc6274692d821d33b59acb6ff615e350c1.tar.bz2 linux-c5db2cfc6274692d821d33b59acb6ff615e350c1.zip |
block: call blk_mq_exit_queue from disk_release for never added disks
To undo the all initialization from blk_mq_init_allocated_queue in case
of a probe failure where add_disk is never called we have to call
blk_mq_exit_queue from put_disk.
This relies on the fact that drivers always call blk_mq_free_tag_set
after calling put_disk in the probe error path if they have a gendisk
at all.
We should be doing this in general, but can't do it for the normal
teardown case (yet) as the tagset can be gone by the time the disk is
released once it was added. I hope to sort this out properly eventually
but for now this isolated hack will do it.
Fixes: 6f8191fdf41d ("block: simplify disk shutdown")
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Link: https://lore.kernel.org/r/20220720130541.1323531-2-hch@lst.de
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/bdev.c')
0 files changed, 0 insertions, 0 deletions