----- Forwarded message from Bastian Blank <[email protected]> ----- Date: Mon, 6 Jul 2026 08:50:35 +0200 From: Bastian Blank <[email protected]> To: [email protected] Subject: Bug#1141434: linux-image-6.12.94+deb13-amd64: regression in loop devices X-Spam-Status: No, score=-5.8 tagged_above=-9999 required=6.31 tests=[DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=disabled Reply-To: Bastian Blank <[email protected]>, [email protected]
Control: tag -1 moreinfo On Sat, Jul 04, 2026 at 10:08:13PM +0200, Cyril Brulebois wrote: > Bastian Blank <[email protected]> (2026-07-04): > > On Sat, Jul 04, 2026 at 07:27:29PM +0200, Cyril Brulebois wrote: > > > root@iot-isobuilder-52:~# fallocate -l 1G foo.img > > > root@iot-isobuilder-52:~# kpartx -asv foo.img > > Why kpartx and not losetup -P? kpartx uses device mapper, while losetup > > -P uses the internal partition support of the kernel. > That's been working for me for many years, and I never noticed losetup > -P until today. kpartx also happens to be what's used by vmdb2 in > various recipes, including the basis for that particular image build. Please try replacing kpartx with losetup. Bastian -- Pain is a thing of the mind. The mind can be controlled. -- Spock, "Operation -- Annihilate!" stardate 3287.2 ----- End forwarded message ----- -- The best diplomat I know is a fully activated phaser bank. -- Scotty
