Public bug reported: Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and "unbind" to the Linux device model which resulted in a number of software issues.
So in this PR [1] which minimize issues resulting from this kernel change (but not avoid them entirely) by make uevent "sticky", meaning that once a tag is assigned to a device it will not be removed from the device again until the device itself is removed (i.e. unplugged). [0] https://lwn.net/Articles/837033/ [1] https://github.com/systemd/systemd/pull/16853/files ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and "unbind" to the Linux device model which resulted in a number of software issues. - So in this PR [1] which minimize issues resulting from this kernel change (but not avoid them entirely) by make uevent "sticky", meaning that once a tag is assigned to a device it will not - be removed from the device again until the device itself is removed (i.e. unplugged). - + So in this PR [1] which minimize issues resulting from this kernel + change (but not avoid them entirely) by make uevent "sticky", meaning + that once a tag is assigned to a device it will not be removed from the + device again until the device itself is removed (i.e. unplugged). [0] https://lwn.net/Articles/837033/ [1] https://github.com/systemd/systemd/pull/16853/files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906653 Title: Backport systemd to make uevents "sticky" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
