> I originally did the slightly lax check because it helps userland
> (lfs_cleanerd, as reported here, mountd and rpc.lockd are using NFSV3_FHMAX
> too) slighly, and also  should be harmless (the value is checked for valid
> range before, and for truncation after the copyin).

mountd shouldn't be affected as it doesn't use fhopen.

> Yamamoto-san, is this kernel change ok with you or should we adapt userland
> to the strict version? The tmpfs regression suite does it right, but I'm not
> sure how easy it will be with rpc.lockd.

it's better to adapt userland.  otherwise, we have to keep
fid_len as syscall abi.

lockd should use the size taken from requests.  i will do it later.

YAMAMOTO Takashi