>>>>> " " == Jamie Lokier <email@example.com> writes:
> Alexander Viro wrote:
>> > I'd be happy with this - admit up front that the data is not
>> > always available. Sometimes the filesystem might _wish_ for
>> > it, but we can't always have what we wish for ;)
>> Wonderful. If that is done (and ->readpage() on symlinks falls
>> into that cathegory - no struct file* around) I have no
>> problems with passing struct file *.
> I have one question. Does this work with NFS servers that
> return different symlink values for different users? Or is
> that still reliable by turning off cacheing at the client?
That's broken at the moment.
If the change of 'symlink' causes cache invalidation then it should
work if you turn off caching. In other words, currently the symlink
change would have to change either i_mtime or i_size on the inode.
Of course we can fix this for the special case of symlinks if so
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:11 EST