That's correct. The other detail that seems to be important is that the user making the call must be different from the user owning the file. We've also been using user remapping on the server, so that non-xattr calls succeed in that configuration. The reproducer James added in the bugzilla is: (on machine with IP address 10.1.1.1) sudo mkdir /nfs_test sudo useradd -u 10000 test_user sudo chown test_user /nfs_test echo "/nfs_test 10.1.1.2(rw,all_squash,anonuid=10000)" | sudo tee -a /etc/exports sudo exportfs -a (on machine with IP address 10.1.1.2) sudo mkdir /nfs_test sudo mount -t nfs -o vers=3,noacl 10.1.1.1:/nfs_test /nfs_test touch /nfs_test/foo install -m 755 /nfs_test/foo /nfs_test/bar - Nelson On Mon, Mar 21, 2016 at 7:43 AM Christoph Hellwig <hch@xxxxxx> wrote: > > Hi Nelson, > > this was indeed most likely caused by my patch. Just to narrow things > down can your clarify that the scenarious is that you have CONFIG_NFS_V3 > set on your client, you're talking to a server not supporting ACLs > at all, and a tool trying to set an ACL is getting the wrong return > value? If so I should be able to reproduce this locally. -- 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
