On Thu, 20 Jul 2023 11:30:31 -0300, Mauricio Faria de Oliveira wrote:
> Apparently, there's an unintended consequence of the improvement for max_loop=0
> in commit 85c50197716c ("loop: Fix the max_loop commandline argument treatment
> when it is set to 0") which might break programs that handle /dev/loop devices.
>
> The (deprecated) autoloading path fails (ENXIO) if the requested minor number
> is greater than or equal to the (new) default (CONFIG_BLK_DEV_LOOP_MIN_COUNT),
> when [loop.]max_loop is not specified. This behavior used to work previously.
>
> [...]
Applied, thanks!
[1/2] loop: deprecate autoloading callback loop_probe()
commit: 23881aec85f3219e8462e87c708815ee2cd82358
[2/2] loop: do not enforce max_loop hard limit by (new) default
commit: bb5faa99f0ce40756ab7bbbce4f16c01ca5ebd5a
Best regards,
--
Jens Axboe
