diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2018-11-26 01:13:08 +0300 |
|---|---|---|
| committer | Jason Gunthorpe <jgg@mellanox.com> | 2018-11-30 03:10:06 +0300 |
| commit | b024dd0eba6e6d568f69d63c5e3153aba94c23e3 (patch) | |
| tree | f9eadb281eab0d4ba7ef2fb49877756134a12fce /tools/perf/scripts/python/syscall-counts-by-pid.py | |
| parent | bfc5d839184f53cc16d551873f9254f2d4d493be (diff) | |
| download | linux-b024dd0eba6e6d568f69d63c5e3153aba94c23e3.tar.xz | |
rxe: IB_WR_REG_MR does not capture MR's iova field
FRWR memory registration is done with a series of calls and WRs.
1. ULP invokes ib_dma_map_sg()
2. ULP invokes ib_map_mr_sg()
3. ULP posts an IB_WR_REG_MR on the Send queue
Step 2 generates an iova. It is permissible for ULPs to change this
iova (with certain restrictions) between steps 2 and 3.
rxe_map_mr_sg captures the MR's iova but later when rxe processes the
REG_MR WR, it ignores the MR's iova field. If a ULP alters the MR's iova
after step 2 but before step 3, rxe never captures that change.
When the remote sends an RDMA Read targeting that MR, rxe looks up the
R_key, but the altered iova does not match the iova stored in the MR,
causing the RDMA Read request to fail.
Reported-by: Anna Schumaker <schumaker.anna@gmail.com>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions
