Re: [fuse-devel] Iozone problem

[Miklos S. <mi...@sz...>]

> > But now there's another problem.  Permission won't be checked even if
> > the file wasn't newly created.  This is bad, the user can now open for
> > writing a file which write permission is disabled.
> >
> > This isn't solvable with 2.3.0 and older FUSE.  2.4 will have an
> > access() method that (if defined) will be called before open (if
> > needed).
> 
> But if the fuse option "default_permissions" is set, then aren't the
> permissions checked in the kernel before a call to open?

Yes, with the 'default_permissions' mount option, this is not a
problem.

But with some filesystems 'default_permissions' is not a solution,
because the permissions simply cannot be calculated from the owner,
group and mode.  An example is sshfs, where the uid/gid on the remote
server has no meaning on the client.

> I use a workaround similar to what you described, but my filesystem
> defaults to setting default_permissions flag, and I'm not able to
> edit a file which is marked read-only..

It's how it should work :)

Miklos