> On Sep 5, 2016, at 13:19, J. R. Okajima <hooanon05g@xxxxxxxxx> wrote: > > > Hello again, > > linux-v4.8-rcN has a commit > 337684a 2016-08-07 fs: return EPERM on immutable inode > > I am afraid NFS should follow the same behaviour. In other words, > fs/nfs/dir.c:nfs_do_access() should return -EPERM when MAY_WRITE on an > immutable inode. Currently it returns EACCES. > The NFS protocol has no way to convey to the client that the inode is labeled as immutable on the server. The NFSv4.1 “retention_hold” mechanism described in RFC5661 comes close, and could possibly be used, but it is not implemented for now. Note also that file immutability is not a POSIX concept, and EPERM is consequently not listed as one of the POSIX sanctioned return values for access(): http://pubs.opengroup.org/onlinepubs/9699919799/functions/access.html Cheers Trond -- 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
