Re: [PATCH] 2.4.8-pre3 fsync entire path (+reiserfs fsync semantic

Alexander Viro (viro@math.psu.edu)
Fri, 3 Aug 2001 19:15:59 -0400 (EDT)


On Sat, 4 Aug 2001, Chris Wedgwood wrote:

> On Fri, Aug 03, 2001 at 06:45:47PM -0400, Alexander Viro wrote:
>
> nfs_fsync().
>
> Ah, well... then I'm not sure how the loop should look. I use
> f->fsync(file, dentry, ...) where file references the original file
> not any of the parent path components.
>
> Obviously, for ext2 and reiserfs (which is what I have here) this
> won't matter --- will it for NFS? If so, so I need to open/etc. for
> each parent component to get a valid struct file*?

<shrug> credentials cache. 2.5 fodder. Notice that with NFS you don't
have fsync for directories. At all. So that's not a problem in that
particular case - you can pass NULL on all subsequent iterations.
On the first step you need struct file * - NFS needs credentials
to pass to the server.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/