Commit 952d07ac authored by Jeff Moyer's avatar Jeff Moyer Committed by Greg Kroah-Hartman

nbd: blk_mq_init_queue returns an error code on failure, not NULL


[ Upstream commit 25b4acfc ]

Additionally, don't assign directly to disk->queue, otherwise
blk_put_queue (called via put_disk) will choke (panic) on the errno
stored there.

Bug found by code inspection after Omar found a similar issue in
virtio_blk.  Compile-tested only.
Signed-off-by: default avatarJeff Moyer <jmoyer@redhat.com>
Reviewed-by: default avatarOmar Sandoval <osandov@fb.com>
Reviewed-by: default avatarJosef Bacik <jbacik@fb.com>
Signed-off-by: default avatarJens Axboe <axboe@fb.com>
Signed-off-by: default avatarSasha Levin <alexander.levin@verizon.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent 44d52834
...@@ -929,6 +929,7 @@ static int __init nbd_init(void) ...@@ -929,6 +929,7 @@ static int __init nbd_init(void)
return -ENOMEM; return -ENOMEM;
for (i = 0; i < nbds_max; i++) { for (i = 0; i < nbds_max; i++) {
struct request_queue *q;
struct gendisk *disk = alloc_disk(1 << part_shift); struct gendisk *disk = alloc_disk(1 << part_shift);
if (!disk) if (!disk)
goto out; goto out;
...@@ -954,12 +955,13 @@ static int __init nbd_init(void) ...@@ -954,12 +955,13 @@ static int __init nbd_init(void)
* every gendisk to have its very own request_queue struct. * every gendisk to have its very own request_queue struct.
* These structs are big so we dynamically allocate them. * These structs are big so we dynamically allocate them.
*/ */
disk->queue = blk_mq_init_queue(&nbd_dev[i].tag_set); q = blk_mq_init_queue(&nbd_dev[i].tag_set);
if (!disk->queue) { if (IS_ERR(q)) {
blk_mq_free_tag_set(&nbd_dev[i].tag_set); blk_mq_free_tag_set(&nbd_dev[i].tag_set);
put_disk(disk); put_disk(disk);
goto out; goto out;
} }
disk->queue = q;
/* /*
* Tell the block layer that we are not a rotational device * Tell the block layer that we are not a rotational device
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment