Commit b390c2b5 authored by Trond Myklebust's avatar Trond Myklebust

SUNRPC: An ENOMEM error from call_encode is always fatal

The special 'ENOMEM' case that was previously flagged as non-fatal is
bogus: auth_gss always returns EAGAIN for non-fatal errors, and may in fact
return ENOMEM in the special case where xdr_buf_read_netobj runs out of
preallocated buffer space (invariably a _fatal_ error, since there is no
provision for preallocating larger buffers).
Signed-off-by: default avatarTrond Myklebust <Trond.Myklebust@netapp.com>
parent 8b39f2b4
...@@ -888,10 +888,6 @@ call_encode(struct rpc_task *task) ...@@ -888,10 +888,6 @@ call_encode(struct rpc_task *task)
task->tk_status = rpcauth_wrap_req(task, encode, req, p, task->tk_status = rpcauth_wrap_req(task, encode, req, p,
task->tk_msg.rpc_argp); task->tk_msg.rpc_argp);
if (task->tk_status == -ENOMEM) {
/* XXX: Is this sane? */
task->tk_status = -EAGAIN;
}
} }
/* /*
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment