On Tue, 2018-02-06 at 10:44 +0100, Danil Kipnis wrote: > the configuration (which devices can be accessed by a particular > client) can happen also after the kernel target module is loaded. The > directory in <dev_search_path> is a module parameter and is fixed. It > contains for example "/ibnbd_devices/". But a particular client X > would be able to only access the devices located in the subdirectory > "/ibnbd_devices/client_x/". (The sessionname here is client_x) One can > add or remove the devices from that directory (those are just symlinks > to /dev/xxx) at any time - before or after the server module is > loaded. But you are right, we need something additional in order to be > able to specify which devices a client can access writable and which > readonly. May be another subdirectories "wr" and "ro" for each client: > those under /ibnbd_devices/client_x/ro/ can only be read by client_x > and those in /ibnbd_devices/client_x/wr/ can also be written to? Please use a standard kernel filesystem (sysfs or configfs) instead of reinventing it. Thanks, Bart.
