[Fakeroot-devel] chown on NFS mounts can produce EINVAL instead of EPERM

[Clint Adams]

On Sat, Aug 22, 2015 at 11:44:52AM -0500, Albert Lee wrote:
> I've encountered problems constructing root filesystems with fakeroot on NFS.
> 
> The chown(2) family of syscalls produces EINVAL when a UID or GID is
> "out of range". On an NFSv4 mount, this can occur when no name mapping
> exists for the UID or GID. The real root user would also receive the error.
> 
> fakeroot only ignores EPERM at the moment. I believe it should be safe
> to accept EINVAL and override policy on range restrictions here.
> 
> Thoughts? (Hopefully someone is reading this list).

Hi Albert,

Which platform is this?  How do you suggest to handle situations wherein
EINVAL is a useful error for the caller (like with fchown() on FreeBSD
or fchownat() on Debian, perhaps)?