Regression in partition table management in kernel 5.15.0-94.104

[Pierre Riteau]

There is a regression in partition table management in the latest jammy kernel which can be reproduced with this simple script:

fallocate -l 32M /tmp/blob
LOOPDEV=$(losetup -f)
sudo losetup $LOOPDEV /tmp/blob
sudo /usr/sbin/parted -s -m $LOOPDEV -- "mklabel gpt"

Expected result:

Partition table is created successfully, exit code is 0, no output.

Actual result:

Partition table is created successfully, but exit code is 1 and output is:

Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128 on /dev/loop3 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.

Packaging information:

Description: Ubuntu 22.04.3 LTS
Release: 22.04

Affected kernel version: Ubuntu 5.15.0-94.104-generic 5.15.136
Last working kernel version: Ubuntu 5.15.0-92.102-generic 5.15.131

[Stratos Zolotas (baskin)]

It may have to do with this issue also.

https://github.com/longhorn/longhorn/issues/6887

It is confirmed by several longhorn users after updating to kernel 5.15.0-94. Previous kernel works as expected.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.