On Fri, Feb 25, 2022 at 07:14:40PM +0100, Christoph Hellwig wrote: > 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@xxxxxxxxxx> > Signed-off-by: Christoph Hellwig <hch@xxxxxx> I'm saddened by the fact that we're not going to get an idea of how far and wide the stupid mknod prior to modprobe use is by making this as y default even though I know this is the right thing to do. I think our ownly measure of success here is to really push Linux distributions to start disabling BLOCK_LEGACY_AUTOLOAD and getting their help to see what burts into flames. Without that endevour we're positioning ourselves to keep the stupid BLOCK_LEGACY_AUTOLOAD forever. I *thought* that for some odd uses cases, maybe early-init, or virt-io, mknod might be used to this day, because of some odd boot failures I saw with linux-next, but I'm no longer seeing those boot failures anymore and I cannot confirm. Luis
