summaryrefslogtreecommitdiffstats
path: root/net/bluetooth
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2015-03-30 20:34:02 +0200
committerAnna Schumaker <Anna.Schumaker@Netapp.com>2015-03-31 15:52:52 +0200
commit805272406a980cab0e11742e5423ba97b6f38836 (patch)
tree89f49bc3a2d999fe4c67339fef0cb767eccaf7b1 /net/bluetooth
parentxprtrdma: Perform a full marshal on retransmit (diff)
downloadlinux-805272406a980cab0e11742e5423ba97b6f38836.tar.xz
linux-805272406a980cab0e11742e5423ba97b6f38836.zip
xprtrdma: Byte-align FRWR registration
The RPC/RDMA transport's FRWR registration logic registers whole pages. This means areas in the first and last pages that are not involved in the RDMA I/O are needlessly exposed to the server. Buffered I/O is typically page-aligned, so not a problem there. But for direct I/O, which can be byte-aligned, and for reply chunks, which are nearly always smaller than a page, the transport could expose memory outside the I/O buffer. FRWR allows byte-aligned memory registration, so let's use it as it was intended. Reported-by: Sagi Grimberg <sagig@mellanox.com> Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Tested-by: Devesh Sharma <Devesh.Sharma@Emulex.Com> Tested-by: Meghana Cheripady <Meghana.Cheripady@Emulex.Com> Tested-by: Veeresh U. Kokatnur <veereshuk@chelsio.com> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'net/bluetooth')
0 files changed, 0 insertions, 0 deletions