diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2016-09-13 16:52:50 +0200 |
|---|---|---|
| committer | J. Bruce Fields <bfields@redhat.com> | 2016-09-23 16:18:52 +0200 |
| commit | cace564f8b6260e806f5e28d7f192fd0e0c603ed (patch) | |
| tree | e20368a823dcfb07faeea2d9bdfb21c6dbd43358 /crypto/dh_helper.c | |
| parent | nfsd: fix dprintk in nfsd4_encode_getdeviceinfo (diff) | |
| download | linux-cace564f8b6260e806f5e28d7f192fd0e0c603ed.tar.xz linux-cace564f8b6260e806f5e28d7f192fd0e0c603ed.zip | |
svcrdma: Tail iovec leaves an orphaned DMA mapping
The ctxt's count field is overloaded to mean the number of pages in
the ctxt->page array and the number of SGEs in the ctxt->sge array.
Typically these two numbers are the same.
However, when an inline RPC reply is constructed from an xdr_buf
with a tail iovec, the head and tail often occupy the same page,
but each are DMA mapped independently. In that case, ->count equals
the number of pages, but it does not equal the number of SGEs.
There's one more SGE, for the tail iovec. Hence there is one more
DMA mapping than there are pages in the ctxt->page array.
This isn't a real problem until the server's iommu is enabled. Then
each RPC reply that has content in that iovec orphans a DMA mapping
that consists of real resources.
krb5i and krb5p always populate that tail iovec. After a couple
million sent krb5i/p RPC replies, the NFS server starts behaving
erratically. Reboot is needed to clear the problem.
Fixes: 9d11b51ce7c1 ("svcrdma: Fix send_reply() scatter/gather set-up")
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'crypto/dh_helper.c')
0 files changed, 0 insertions, 0 deletions