diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2016-05-04 10:52:55 -0400 |
|---|---|---|
| committer | J. Bruce Fields <bfields@redhat.com> | 2016-05-13 15:53:05 -0400 |
| commit | 6625d0913771df5f12b9531c8cb8414e55f1c21d (patch) | |
| tree | fe2416c9d582062f42d1ac81a58e858a6e994382 /fs/nfsd | |
| parent | 696190eaf168e83fcbf0c9cf087995cdd15807e5 (diff) | |
| download | linux-6625d0913771df5f12b9531c8cb8414e55f1c21d.tar.gz linux-6625d0913771df5f12b9531c8cb8414e55f1c21d.tar.bz2 linux-6625d0913771df5f12b9531c8cb8414e55f1c21d.zip | |
svcrdma: Do not add XDR padding to xdr_buf page vector
An xdr_buf has a head, a vector of pages, and a tail. Each
RPC request is presented to the NFS server contained in an
xdr_buf.
The RDMA transport would like to supply the NFS server with only
the NFS WRITE payload bytes in the page vector. In some common
cases, that would allow the NFS server to swap those pages right
into the target file's page cache.
Have the transport's RDMA Read logic put XDR pad bytes in the tail
iovec, and not in the pages that hold the data payload.
The NFSv3 WRITE XDR decoder is finicky about the lengths involved,
so make sure it is looking in the correct places when computing
the total length of the incoming NFS WRITE request.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/nfsd')
| -rw-r--r-- | fs/nfsd/nfs3xdr.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/nfsd/nfs3xdr.c b/fs/nfsd/nfs3xdr.c index 2246454dec76..c5eff5fde11c 100644 --- a/fs/nfsd/nfs3xdr.c +++ b/fs/nfsd/nfs3xdr.c @@ -379,7 +379,7 @@ nfs3svc_decode_writeargs(struct svc_rqst *rqstp, __be32 *p, */ hdr = (void*)p - rqstp->rq_arg.head[0].iov_base; dlen = rqstp->rq_arg.head[0].iov_len + rqstp->rq_arg.page_len - - hdr; + + rqstp->rq_arg.tail[0].iov_len - hdr; /* * Round the length of the data which was specified up to * the next multiple of XDR units and then compare that |