One imagines that a file opened O_NONE would never, *ever*
call device functions. It would be stopped at the VFS layer.
> Second, file descriptors are currently analagous to capabilities (the
> academic use of the word, *not* the linux use of the word) in that they
> are indications of security that can be passed among processes with
> differing credentials (either across a set[ug]id execve or by passing
> them across a socket) Allowing any process to get a filedescriptor
> without needing read or write permission undermines these basic
> semantics.
Not if the only things that can be done with the file descriptor are
*exactly* the same ones that can be done with a name. No more.
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/