diff options
author | Chuck Lever <chuck.lever@oracle.com> | 2016-06-29 13:53:11 -0400 |
---|---|---|
committer | Anna Schumaker <Anna.Schumaker@Netapp.com> | 2016-07-11 15:50:43 -0400 |
commit | 2dc3a69de0d6e7f4dba7dbf8eadd5c3ac34098c7 (patch) | |
tree | 71fe19a390fc7317e2d6b09e7f25fc1882e8164a /net/rxrpc/ar-ack.c | |
parent | 42fe28f607634841e870acf16b10469824594463 (diff) | |
download | linux-next-2dc3a69de0d6e7f4dba7dbf8eadd5c3ac34098c7.tar.gz |
xprtrdma: Remove ALLPHYSICAL memory registration mode
No HCA or RNIC in the kernel tree requires the use of ALLPHYSICAL.
ALLPHYSICAL advertises in the clear on the network fabric an R_key
that is good for all of the client's memory. No known exploit
exists, but theoretically any user on the server can use that R_key
on the client's QP to read or update any part of the client's memory.
ALLPHYSICAL exposes the client to server bugs, including:
o base/bounds errors causing data outside the i/o buffer to be
accessed
o RDMA access after reply causing data corruption and/or integrity
fail
ALLPHYSICAL can't protect application memory regions from server
update after a local signal or soft timeout has terminated an RPC.
ALLPHYSICAL chunks are no larger than a page. Special cases to
handle small chunks and long chunk lists have been a source of
implementation complexity and bugs.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Tested-by: Steve Wise <swise@opengridcomputing.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'net/rxrpc/ar-ack.c')
0 files changed, 0 insertions, 0 deletions