`systemd-sysext refresh` does print scary warnings

[tormath1]

Description

In current Alpha (4722.0.0) and Beta (4694.1.0) the command sudo systemd-sysext refresh does print scary warnings:

core@localhost ~ $ sudo systemd-sysext refresh
device-mapper: reload ioctl on loop4p1-verity (253:5) failed: Invalid argument
device-mapper: reload ioctl on loop5p1-verity (253:5) failed: Invalid argument
device-mapper: reload ioctl on loop6p1-verity (253:5) failed: Invalid argument
device-mapper: reload ioctl on loop4p1-verity (253:5) failed: Invalid argument
device-mapper: reload ioctl on loop5p1-verity (253:6) failed: Invalid argument
device-mapper: reload ioctl on loop6p1-verity (253:7) failed: Invalid argument
Skipping extension refresh because no change was found, use --always-refresh=yes to always do a refresh.
core@localhost ~ $ sudo systemd-sysext refresh --always-refresh=yes
device-mapper: reload ioctl on loop4p1-verity (253:5) failed: Invalid argument
device-mapper: reload ioctl on loop5p1-verity (253:5) failed: Invalid argument
device-mapper: reload ioctl on loop6p1-verity (253:5) failed: Invalid argument
device-mapper: reload ioctl on loop4p1-verity (253:5) failed: Invalid argument
device-mapper: reload ioctl on loop5p1-verity (253:6) failed: Invalid argument
device-mapper: reload ioctl on loop6p1-verity (253:7) failed: Invalid argument
Using extensions 'containerd-flatcar.raw', 'docker-flatcar.raw', 'oem-qemu-4694.1.0.raw'.
Unmerged '/usr'.
Merged extensions into '/usr'.

Impact

It does not seem to have impacts on the actual command but can be confusing and symptoms of another issue.

Environment and steps to reproduce

Boot a version >= 4694 (I did not check but it might happen earlier but not before 4593) and run sudo systemd-sysext refresh

Expected behavior

No warnings.