diff options
author | Chuck Lever <chuck.lever@oracle.com> | 2016-09-15 16:55:20 +0200 |
---|---|---|
committer | Anna Schumaker <Anna.Schumaker@Netapp.com> | 2016-09-19 19:08:37 +0200 |
commit | 5fe6eaa1f9a00b9a5927e3b791ecad2f3eaab130 (patch) | |
tree | 3b5b516ef941eb91452458260d08b3473491913c /.mailmap | |
parent | SUNRPC: Refactor rpc_xdr_buf_init() (diff) | |
download | linux-5fe6eaa1f9a00b9a5927e3b791ecad2f3eaab130.tar.xz linux-5fe6eaa1f9a00b9a5927e3b791ecad2f3eaab130.zip |
SUNRPC: Generalize the RPC buffer allocation API
xprtrdma needs to allocate the Call and Reply buffers separately.
TBH, the reliance on using a single buffer for the pair of XDR
buffers is transport implementation-specific.
Transports that want to allocate separate Call and Reply buffers
will ignore the "size" argument anyway. Don't bother passing it.
The buf_alloc method can't return two pointers. Instead, make the
method's return value an error code, and set the rq_buffer pointer
in the method itself.
This gives call_allocate an opportunity to terminate an RPC instead
of looping forever when a permanent problem occurs. If a request is
just bogus, or the transport is in a state where it can't allocate
resources for any request, there needs to be a way to kill the RPC
right there and not loop.
This immediately fixes a rare problem in the backchannel send path,
which loops if the server happens to send a CB request whose
call+reply size is larger than a page (which it shouldn't do yet).
One more issue: looks like xprt_inject_disconnect was incorrectly
placed in the failure path in call_allocate. It needs to be in the
success path, as it is for other call-sites.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions