Re: NFS sillyrename side effect

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 18 Oct 2010 15:48:11 +0100 ClÃudio Martins <ctpm@xxxxxxxxxx> wrote:
> 
>  Section D2 ends with:
> 
> "The NFS version 4 protocol is stateful, and could actually support
> delete-on-last-close. Unfortunately there isn't an easy way to do this
> and remain backwards-compatible with version 2 and 3 accessors."
> 
>  So, theoretically, could one modify the code to selectively disable
> silly rename on a client, when it knows it is talking v4 with the
> server?
> 

 BTW, to clarify, I'm assuming a scenario where the server is
configured to talk v4 only, which I suspect should be common, at least
when you're relying on v4 kerberos security.

Best regards

ClÃudio

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux