Re: [libvirt] [systemd-devel] Suspending access to opened/active /dev/nodes during application runtime

>> Problem: >> Has anyone thought about a mechanism to limit/remove an access to a >> device during an application runtime? Meaning we have an >> application that has an open file descriptor to some /dev/node and >> depending on *something* it gains or looses the access to it >> gracefully (with or without a notification, but without any fatal >> consequences). > > logind can mute input devices as sessions are switched, to enable > unpriviliged X11 and wayland compositors. Would you please elaborate on this? Where is this mechanism? How does it work without kernel space support? Is there some kernel space support I’m not aware of?

> Before you think about doing something like this, you need to fix the > kernel to provide namespaced devices (good luck!) Precisly! That’s the generic idea. I’m not for implementing it though at this moment. I just wanted to know whether anybody actually though about it or maybe someone is interested in starting such a work, etc.

> logind can do this for you between sessions. But such a container setup > will never work without proper device namespacing. So how can it do it when there is no kernel support? You mean it could be doing this if the support were there?