diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2026-05-15 11:35:14 -0400 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2026-05-15 17:49:23 +0200 |
| commit | fbaee2a5c406f274d72ed8f98bf9140ae43c5972 (patch) | |
| tree | 6bec18301fee645d8b323c09a34f50552d0be122 /drivers/platform/wmi/tests/git@git.tavy.me:linux.git | |
| parent | 3aa75b92e862490b8744b659a5a906f1dc6cb951 (diff) | |
nfsd: Map -ESTALE from case probe to NFS3ERR_STALE
The PATHCONF switch in nfsd3_proc_pathconf() recognizes -EOPNOTSUPP
(filesystem does not expose case state) and maps -EACCES / -EPERM to
nfserr_stale, but lets every other errno fall through to
nfserr_serverfault. -ESTALE escapes the same way even though RFC 1813
lists NFS3ERR_STALE as a permitted PATHCONF status, so a probe of an
NFS-backed re-export whose parent dentry has been invalidated returns
SERVERFAULT and tells the client the server is broken when the handle
itself simply went stale.
Add an explicit -ESTALE arm that maps to nfserr_stale.
Fixes: a8de9c3b40e4 ("nfsd: Report export case-folding via NFSv3 PATHCONF")
Reported-by: sashiko-bot <sashiko-bot@kernel.org>
Closes: https://sashiko.dev/#/patchset/20260507-case-sensitivity-v14-0-e62cc8200435@oracle.com?part=13
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Link: https://patch.msgid.link/20260515153515.362266-7-cel@kernel.org
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'drivers/platform/wmi/tests/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions
