so we seem to have indeed another udev race here. The patch from suse looks quite hackish to me (calling udevsettle() with system() to calm things down), which is a workaround in cryptsetup but not a real fix.
udev maintainers, what do you think about this bug? can this be fixed in udev, or shall we take suse's patch?
so we seem to have indeed another udev race here. The patch from suse looks quite hackish to me (calling udevsettle() with system() to calm things down), which is a workaround in cryptsetup but not a real fix.
udev maintainers, what do you think about this bug? can this be fixed in udev, or shall we take suse's patch?