Searched hist:"451 f0b6f4c44d7b649ae609157b114b71f6d7875" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/block/ |
| H A D | bdev.c | diff 451f0b6f4c44d7b649ae609157b114b71f6d7875 Fri Feb 25 12:14:40 CST 2022 Christoph Hellwig <hch@lst.de> 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>
|
| H A D | Kconfig | diff 451f0b6f4c44d7b649ae609157b114b71f6d7875 Fri Feb 25 12:14:40 CST 2022 Christoph Hellwig <hch@lst.de> 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>
|