On Tue, 15 May 2001, H. Peter Anvin wrote:

> Permission management.  The permissions on the subnodes are inherited
> from the main node, which is stored on a persistent medium.

If you want them all to inherit it - inherit from mountpoint. End of story.
Yes, it means that permission(9) will need vfsmount argument. But we
_will_ need that anyway. For per-mountpoint read-only, if nothing else.

Want details? Please. We have the ->getattr() method. Currently not
used, but intended to be used by ...stat family (with the current
behaviour being default). Now, let's pass to permission(9), notify_change(9)
and ->{set,get}attr()  both vfsmount and dentry. See what I mean?

We get (essentially for free)
        * per-mountpoint read-only flag (I've already done nosuid, noexec
and nodev per-mountpoint)
        * ability to have inodes that simply don't have owners - ownership
is determined (and handled) by the functions/methods above. So FAT and
friends can get rid of knowledge of uid=,gid=" crap.
        * ability to inherit ownership from mountpoint and if fs wants it -
update the ownership of mountpoint.

-
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/

Reply via email to