I started a fresh VM, with 5.15.0-101-generic from updates. I ran the following reproducer:
$ fallocate -l 1G /tmp/blob
$ LOOPDEV=$(sudo losetup --find --show /tmp/blob)
$ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt mkpart primary 0% 100%
Error: Partition(s) 1 on /dev/loop4 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.
I then enabled -proposed, and installed 5.15.0-102-generic:
$ uname -rv
5.15.0-102-generic #112-Ubuntu SMP Tue Mar 5 16:50:32 UTC 2024
Performing verification for Jammy.
I started a fresh VM, with 5.15.0-101-generic from updates. I ran the following reproducer:
$ fallocate -l 1G /tmp/blob
$ LOOPDEV=$(sudo losetup --find --show /tmp/blob)
$ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt mkpart primary 0% 100%
Error: Partition(s) 1 on /dev/loop4 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.
I then enabled -proposed, and installed 5.15.0-102-generic:
$ uname -rv
5.15.0-102-generic #112-Ubuntu SMP Tue Mar 5 16:50:32 UTC 2024
Running the reproducer:
$ fallocate -l 1G /tmp/blob
$ LOOPDEV=$(sudo losetup --find --show /tmp/blob)
$ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt mkpart primary 0% 100%
$ losetup -a
/dev/loop4: []: (/tmp/blob)
$ ll /dev
...
brw-rw---- 1 root disk 7, 4 Mar 19 03:45 loop4
brw-rw---- 1 root disk 259, 0 Mar 19 03:45 loop4p1
...
Things are now working as intended. The kernel in -proposed solves the issue. Happy to mark verified for Jammy.