diff options
| author | Christoph Hellwig <hch@lst.de> | 2022-02-25 19:14:40 +0100 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2022-02-27 14:49:23 -0700 |
| commit | 451f0b6f4c44d7b649ae609157b114b71f6d7875 (patch) | |
| tree | 19e10226c0541f8fca6b749533b69e2e4f89092c /block/Kconfig | |
| parent | 86d7331299fda7634b11c1b7c911432679d525a5 (diff) | |
block: default BLOCK_LEGACY_AUTOLOAD to y
As Luis reported, losetup currently doesn't properly create the loop
device without this if the device node already exists because old
scripts created it manually. So default to y for now and remove the
aggressive removal schedule.
Reported-by: Luis Chamberlain <mcgrof@kernel.org>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Link: https://lore.kernel.org/r/20220225181440.1351591-1-hch@lst.de
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/Kconfig')
| -rw-r--r-- | block/Kconfig | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/block/Kconfig b/block/Kconfig index 168b873eb666..7eb5d6d53b3f 100644 --- a/block/Kconfig +++ b/block/Kconfig @@ -28,15 +28,13 @@ if BLOCK config BLOCK_LEGACY_AUTOLOAD bool "Legacy autoloading support" + default y help Enable loading modules and creating block device instances based on accesses through their device special file. This is a historic Linux feature and makes no sense in a udev world where device files are - created on demand. - - Say N here unless booting or other functionality broke without it, in - which case you should also send a report to your distribution and - linux-block@vger.kernel.org. + created on demand, but scripts that manually create device nodes and + then call losetup might rely on this behavior. config BLK_RQ_ALLOC_TIME bool |