Alan Cox <[EMAIL PROTECTED]> wrote: > > On Llu, 2005-09-05 at 02:19 -0700, Andrew Morton wrote: > > > create_lockspace() > > > release_lockspace() > > > lock() > > > unlock() > > > > Neat. I'd be inclined to make them syscalls then. I don't suppose anyone > > is likely to object if we reserve those slots. > > If the locks are not file descriptors then answer the following: > > - How are they ref counted > - What are the cleanup semantics > - How do I pass a lock between processes (AF_UNIX sockets wont work now) > - How do I poll on a lock coming free. > - What are the semantics of lock ownership > - What rules apply for inheritance > - How do I access a lock across threads. > - What is the permission model. > - How do I attach audit to it > - How do I write SELinux rules for it > - How do I use mount to make namespaces appear in multiple vservers > > and thats for starters...
Return an fd from create_lockspace(). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
