Hi all, I guess it's time to tick off yet another item on my long-term to-do list: Block namespaces ---------------- Idea is similar to what network already does: allowing each user namespace to have a different 'view' on the existing block devices. EG if the admin creates a ramdisk in one namespace this device should not be visible to other namespaces. But for me the most important use-case would be qemu; currently the devices need to be set up in the host, even though the host has no business touching it as they really belong to the qemu instance. This is causing quite some irritation eg when this device has LVM or MD metadata and udev is trying to activate it on the host. Overall plan is to restrict views of '/dev', '/sys/dev/block' and '/sys/block' to only present the devices 'visible' for this namespace. Initially the drivers would keep their global enumeration, but plan is to make the drivers namespace-aware, too, such that each namespace could have its own driver-specific device enumeration. Goal of this topic is to get a consensus on whether block namespaces are a feature which would find interest, and also to discuss some design details here: - Only in certain cases can a namespace be assigned (eg by calling 'modprobe', starting iscsiadm, or calling nvme-cli); how do we handle devices for which no namespace can be identified? - Shall we allow for different device enumeration per namespace? - Into which level should we go with hiding sysfs structures? Is blanking out the higher-level interfaces in /dev and /sys/block enough? Cheers, Hannes -- Dr. Hannes Reinecke Kernel Storage Architect hare@xxxxxxx +49 911 74053 688 SUSE Software Solutions Germany GmbH, 90409 Nürnberg GF: F. Imendörffer, HRB 36809 (AG Nürnberg)
