From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: NFS4ERR_DENIED becomes EIO? Date: Wed, 18 Feb 2009 16:19:15 -0500 Message-ID: <499C7B53.5030802@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-fsdevel To: linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Return-path: Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org I think I may have found a tiny NFSv4 client bug. What I am seeing: 1. On Linux NFS client (2.6.29-rc2), issue chown(1) to change the owner of the file (causing SETATTR:OWNER to be issued) 2. My userland NFS server returns NFS4ERR_DENIED for the SETATTR op 3. Linux NFS client returns EIO (I/O error) to userland That was a bit unexpected. I would have guessed EPERM, perhaps. Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html