Skip to content

fix: report unhandled errors as NFS SERVERFAULT, not an RPC fault - #9

Open
AliRamberg wants to merge 1 commit into
masterfrom
fix/handler-errors-as-nfs-status
Open

fix: report unhandled errors as NFS SERVERFAULT, not an RPC fault#9
AliRamberg wants to merge 1 commit into
masterfrom
fix/handler-errors-as-nfs-status

Conversation

@AliRamberg

Copy link
Copy Markdown

An error a procedure handler returns that is neither an RPCError nor an NFSStatusError was formatted as ResponseCodeSystemError, an RPC-level accept_stat fault. A fault signals a malformed RPC, which some clients (macOS surfaces it as EBADRPC) turn into a failed syscall rather than a normal filesystem error.

Map such errors to the NFS status SERVERFAULT inside an accepted reply so the client receives an ordinary I/O error instead.

An error a procedure handler returns that is neither an RPCError nor an
NFSStatusError was formatted as ResponseCodeSystemError, an RPC-level
accept_stat fault.  A fault signals a malformed RPC, which some clients
(macOS surfaces it as EBADRPC) turn into a failed syscall rather than a
normal filesystem error.

Map such errors to the NFS status SERVERFAULT inside an accepted reply so
the client receives an ordinary I/O error instead.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant