On Mon, 2022-01-31 at 14:33 +0100, Peter Rajnoha wrote: > (just discussed this with Zdenek too) > > The patch makes sense to me! > > We added all the DM_UDEV_PRIMARY_SOURCE_FLAG and related for exactly > such cases where we need to take the existing values already scanned > in previous event, main use-case being the trigger at boot. We just > didn't cover the 13-dm-disk.rules with the same logic regarding the > suspended state to keep the symlinks - I didn't think it would cause > issues (because, usually, after suspend, we anticipate incoming > resume where the device is scanned again). > > But yes, if temporarily losing the symlink causes issues, your patch > solves that (Zdenek will push that upstream). Thank you very much! It occured to me that if we want to solve my use case with minimal risk, we could make the the case in which the symlinks are preserved conditional on ACTION=="add" (i.e. true coldplug events). Tell me if you'd prefer that, I can re-submit. Martin -- dm-devel mailing list dm-devel@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/dm-devel
