userspace object manager confused

[Dominick Grift <dac.override@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

I vaguely recall that we discussed this issue or at least that i mentioned it here but i can't recall the outcome if any:

So today on my rawhide system i noticed that i somehow forgot to add support for the smc_socket class (i suspect that is part of the extended socket class patches)

I added the class (which i suppose is unordered like the othe extended socket classes) but as soon as I loaded up the policy with the new unordered smc_socket class the system became unusable.

This is because the dbus object manager became confused due to my adding a new (unordered) class at runtime, and that the dbus class was no longer working.

Modern systems heavily rely on dbus at the heart and so it is undesire-able that this happens.

A reboot clears this issue up but adding (unordered) classes at runtime should not cause these issues i suspect

-- 
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8  02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]