On 2/18/22 8:10 PM, Luis Chamberlain wrote:
> 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...
My guess would be that it's:
commit fbdee71bb5d8d054e1bdb5af4c540f2cb86fe296
Author: Christoph Hellwig <hch@xxxxxx>
Date: Tue Jan 4 08:16:47 2022 +0100
block: deprecate autoloading based on dev_t
--
Jens Axboe
