Re: [PATCH] private mounts

[Jamie Lokier]

Miklos Szeredi wrote:
> > > This is the controversial part in all it's glory:
> > > 
> > > 	if (!(fc->flags & FUSE_ALLOW_OTHER) && current->fsuid != fc->user_id)
> > > 		return -EACCES;
> > > 
> > > Leaving it out would gain us what exactly?
> > 
> > Well, if it brings us ugly semantics, keeping those two lines out for
> > a while can help merge a lot...
> 
> To the mount owner the semantics are quite normal.  Others will be
> denied access to the mountpoint, which doesn't introduce any new
> semantics either.

Why, exactly, is this check in the kernel and not the FUSE daemon?

Someone said the FUSE daemon knows which user is making filesystem
requests, and can therefore do this.  Is it true?

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