The patch below does not apply to the 4.19-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to stable@vger.kernel.org.
Possible dependencies:
85c50197716c ("loop: Fix the max_loop commandline argument treatment when it is set to 0") 18d1f200b380 ("loop: move loop_ctl_mutex locking into loop_add") f9d107644aa4 ("loop: split loop_control_ioctl") 4157fe0b3d16 ("loop: don't call loop_lookup before adding a loop device") d6da83d072c1 ("loop: remove the l argument to loop_add") 990e78116d38 ("block: loop: fix deadlock between open and remove") 6cc8e7430801 ("loop: scale loop device by introducing per device lock") aeb2b0b1a3da ("block: drop dead assignments in loop_init()") 8410d38c2552 ("loop: use __register_blkdev to allocate devices on demand") 200f93377220 ("loop: be paranoid on exit and prevent new additions / removals") 62ab466ca881 ("loop: Move loop_set_status_from_info() and friends up") 0c3796c24459 ("loop: Factor out configuring loop from status") b0bd158dd630 ("loop: Refactor loop_set_status() size calculation") 5795b6f5607f ("loop: Factor out setting loop device size") 083a6a50783e ("loop: Remove sector_t truncation checks") 7c5014b0987a ("loop: Call loop_config_discard() only after new config is applied") 33ec3e53e7b1 ("loop: Don't change loop device under exclusive opener") 56a85fd8376e ("loop: properly observe rotational flag of underlying device") 758a58d0bc67 ("loop: set GENHD_FL_NO_PART_SCAN after blkdev_reread_part()") 5db470e229e2 ("loop: drop caches if offset or block_size are changed")
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From 85c50197716c60fe57f411339c579462e563ac57 Mon Sep 17 00:00:00 2001 From: "Isaac J. Manjarres" isaacmanjarres@google.com Date: Thu, 8 Dec 2022 13:29:01 -0800 Subject: [PATCH] loop: Fix the max_loop commandline argument treatment when it is set to 0
Currently, the max_loop commandline argument can be used to specify how many loop block devices are created at init time. If it is not specified on the commandline, CONFIG_BLK_DEV_LOOP_MIN_COUNT loop block devices will be created.
The max_loop commandline argument can be used to override the value of CONFIG_BLK_DEV_LOOP_MIN_COUNT. However, when max_loop is set to 0 through the commandline, the current logic treats it as if it had not been set, and creates CONFIG_BLK_DEV_LOOP_MIN_COUNT devices anyway.
Fix this by starting max_loop off as set to CONFIG_BLK_DEV_LOOP_MIN_COUNT. This preserves the intended behavior of creating CONFIG_BLK_DEV_LOOP_MIN_COUNT loop block devices if the max_loop commandline parameter is not specified, and allowing max_loop to be respected for all values, including 0.
This allows environments that can create all of their required loop block devices on demand to not have to unnecessarily preallocate loop block devices.
Fixes: 732850827450 ("remove artificial software max_loop limit") Cc: stable@vger.kernel.org Cc: Ken Chen kenchen@google.com Signed-off-by: Isaac J. Manjarres isaacmanjarres@google.com Link: https://lore.kernel.org/r/20221208212902.765781-1-isaacmanjarres@google.com Signed-off-by: Jens Axboe axboe@kernel.dk
diff --git a/drivers/block/loop.c b/drivers/block/loop.c index 1f8f3b87bdfa..df628e30bca4 100644 --- a/drivers/block/loop.c +++ b/drivers/block/loop.c @@ -1773,7 +1773,16 @@ static const struct block_device_operations lo_fops = { /* * And now the modules code and kernel interface. */ -static int max_loop; + +/* + * If max_loop is specified, create that many devices upfront. + * This also becomes a hard limit. If max_loop is not specified, + * create CONFIG_BLK_DEV_LOOP_MIN_COUNT loop devices at module + * init time. Loop devices can be requested on-demand with the + * /dev/loop-control interface, or be instantiated by accessing + * a 'dead' device node. + */ +static int max_loop = CONFIG_BLK_DEV_LOOP_MIN_COUNT; module_param(max_loop, int, 0444); MODULE_PARM_DESC(max_loop, "Maximum number of loop devices"); module_param(max_part, int, 0444); @@ -2181,7 +2190,7 @@ MODULE_ALIAS("devname:loop-control");
static int __init loop_init(void) { - int i, nr; + int i; int err;
part_shift = 0; @@ -2209,19 +2218,6 @@ static int __init loop_init(void) goto err_out; }
- /* - * If max_loop is specified, create that many devices upfront. - * This also becomes a hard limit. If max_loop is not specified, - * create CONFIG_BLK_DEV_LOOP_MIN_COUNT loop devices at module - * init time. Loop devices can be requested on-demand with the - * /dev/loop-control interface, or be instantiated by accessing - * a 'dead' device node. - */ - if (max_loop) - nr = max_loop; - else - nr = CONFIG_BLK_DEV_LOOP_MIN_COUNT; - err = misc_register(&loop_misc); if (err < 0) goto err_out; @@ -2233,7 +2229,7 @@ static int __init loop_init(void) }
/* pre-create number of devices given by config or max_loop */ - for (i = 0; i < nr; i++) + for (i = 0; i < max_loop; i++) loop_add(i);
printk(KERN_INFO "loop: module loaded\n");