Re: usbfs, claiming entire usb devices

[Kay Sievers]

On Thu, May 7, 2009 at 21:55, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote:
> There is a proposal afoot to give user programs the ability to claim
> ownership of an entire USB device, rather than just individual
> interfaces. ÂIn fact, we'd like processes to be able to own whatever
> device gets plugged into a particular port on a particular hub.
>
> The question is how the API should work. ÂA simple approach is to have
> a sysfs or usbfs file correspond to each port; when a process opens the
> file it would be granted ownership of any device plugged into that
> port. ÂSince the file is automatically closed when the process ends, we
> wouldn't have to worry about ownership never getting released.
>
> But there's a snag. ÂWhen a process goes to open the usbfs file for a
> device, the kernel needs to know whether or not the process owns that
> device. ÂIn other words, we need to figure out whether or not the
> process has opened the corresponding port file.
>
> Is there a simple way to do this? ÂIs it reasonable to search through
> all the process's fd's, looking for one that matches a particular
> inode?
>
> Or would a completely different API approach be better?

You have one file per device, and that file has normal unix file
permissions. Userspace can grant access to that file by ownership or
by adding an ACL. What else do we need? Why would the kernel care who
opened the file, when the one was able to get through the normal file
access check?

Or did you mean some magic for an entire tree of devices below some
port? Like some sort of permission inheritance in the kernel?

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/