Re: [EXTERNAL] nfsv4 client idmapper issue

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

 



On 22 Sep 2022, at 10:18, Alan Maxwell wrote:

Again, we would expect ultimately if the server returns error, nfs client should do same, show and error, not change the configuration and ignore our disable_id_mapping.

Not all NFSv4 errors are sent back to userspace, and the meaning of this
error ( I am assuming the server returns NFS4ERR_BADOWNER, a wire capture would verify it ) is to tell the client that it was unable to translate the
owner value.  As I understand RFC 8881, that's a clear indication to the
client that the server is not treating the values as numeric uid/gid, it is
attempting to map them.  That is why the client changes its behavior.

Besides, what error can the chown syscall possibly return in this case?
Let's say the client /doesn't/ re-enable string-based names. What are you
expecting the client to return to userspace?

Ben




[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