Comment 14 for bug 1552241

I've found that on a system with the most recent stack libvirt-3.6 + qemu 2.10 this does no more show up. So it is either fixed and we need to find what to backport or that system is special.

So on that given system I stepped back to libvirt 2.5/qemu 2.8 which I know to show the issue on another system. And it turns out that it is the device that does not trigger the issue there.
So no good place to debug and probably still not fixed on newer versions.

So back to debugging where/why qemu actually calls these.
On that a note: I was made aware that the paths in /run/udev/data are rather unpredictable as they base on minor/major numbers - well maybe they are runtime predictable. But in any case reading there can be racy it seems.