[Bug 1906653] Re: Backport systemd to make uevents "sticky"

[Dan Streetman]

As I mentioned in my last comment, I'm skeptical that the benefit of
backporting would outweigh the potential problems it would introduce to
existing stable releases.

I'm marking this as wont-fix for that reason. I don't think we should
consider this unless you can provide specific examples of significant,
serious problems that would be fixed by backporting the change.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1906653

Title:
  Backport systemd to make uevents "sticky"

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Won't Fix
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  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).

  An example causing by this issue, I had a usb printer (non-ippusbxd)
  which connected to my laptop, but after unplugging it from my laptop,
  the .device unit were still present, if a different printer gets
  plugged to the same USB port then, it won't be configured correctly.

  [0] https://lwn.net/Articles/837033/
  [1] https://github.com/systemd/systemd/pull/16853/files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions