udev: never ask libblkid for detecting superblocks with bad checksums (#6215)
Previously, we'd ask liblkid to also tell us about recognized superblocks with bad checksums. We'd then log about them and ignore them. This however created ambuigity problems, see #6110: the BLKID_SUBLKS_BADCSUM is not as innocent as it appears. This patch drops bad checksum handling and we ignore all such superblocks entirely again, as it was the status quo ante d47f6ca5 (where this was snuck in). Ideally, libblkid would be changed to avoid this ambiguity problems for bad checksums, but that's not going to happen any time soon, according to @karelzak. Fixes: #6110
Loading
Please register or sign in to comment