I noticed that since next-20220211 losetup fails at something stupid simple: losetup $LOOPDEV $DISK I can't see how the changes on drivers/block/loop.c would cause this, I even tried to revert what I thought would be the only commit which would seem to do a functional change "loop: revert "make autoclear operation asynchronous" but that didn't fix it. I proceeded to bisecting... but I did this on today's linux-next, and well today's linux-next is hosed even at boot. My bisection then was completley inconclusive since linux-next is pure poop today. Any ideas though? Fortunately Linus' tree is fine. I'm quit afraid that we wouldn't have caught this issue. Seems pretty straight forward. It would seem we don't have such a basic thing on blktests, so I'll go add that... Luis
