Files
linux-stable-mirror/include/uapi/linux
Chuck Lever 0ac903d1bf NFS: NFSERR_INVAL is not defined by NFSv2
A documenting comment in include/uapi/linux/nfs.h claims incorrectly
that NFSv2 defines NFSERR_INVAL. There is no such definition in either
RFC 1094 or https://pubs.opengroup.org/onlinepubs/9629799/chap7.htm

NFS3ERR_INVAL is introduced in RFC 1813.

NFSD returns NFSERR_INVAL for PROC_GETACL, which has no
specification (yet).

However, nfsd_map_status() maps nfserr_symlink and nfserr_wrong_type
to nfserr_inval, which does not align with RFC 1094. This logic was
introduced only recently by commit 438f81e0e9 ("nfsd: move error
choice for incorrect object types to version-specific code."). Given
that we have no INVAL or SERVERFAULT status in NFSv2, probably the
only choice is NFSERR_IO.

Fixes: 438f81e0e9 ("nfsd: move error choice for incorrect object types to version-specific code.")
Reviewed-by: NeilBrown <neil@brown.name>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
2026-01-26 10:10:58 -05:00
..
2025-11-24 21:56:17 +01:00
2026-01-18 11:22:53 -05:00
2025-10-28 22:59:19 +01:00
2025-11-25 19:20:42 -08:00
2025-11-05 08:07:21 -07:00
2025-09-05 09:11:28 +02:00
2025-05-03 12:02:09 +02:00
2025-11-24 17:52:11 +01:00
2025-11-24 17:52:11 +01:00
2025-11-29 21:39:58 +09:00
2025-12-18 21:34:42 -08:00
2025-09-15 14:32:54 +02:00
2025-07-08 12:39:24 +02:00
2025-12-05 23:16:26 +00:00
2025-11-03 17:41:18 +01:00
2026-01-11 06:09:11 -10:00
2025-10-30 14:25:14 +01:00
2025-11-25 19:20:42 -08:00
2025-11-04 08:30:09 +01:00
2025-07-14 18:41:42 -07:00
2025-06-19 14:28:22 +02:00
2025-05-21 13:41:03 +02:00
2025-04-17 12:30:02 +02:00
2025-09-21 17:44:20 -04:00
2025-09-22 09:29:28 +01:00
2025-11-30 18:02:43 -05:00
2025-05-27 10:27:54 -04:00
2025-09-22 09:29:29 +01:00