mirror of
https://github.com/torvalds/linux
synced 2024-10-27 05:39:25 +00:00
cf570a9374
When the Linux NFS server writes an odd-length data item into a Write chunk, it finishes with XDR pad bytes. If the data item is smaller than the Write chunk, the pad bytes are written at the end of the data item, but still inside the chunk (ie, in the application's buffer). Since this is direct data placement, that exposes the pad bytes. XDR pad bytes are inserted in order to preserve the XDR alignment of the next XDR data item in an XDR stream. But Write chunks do not appear in the payload XDR stream, and only one data item is allowed in each chunk. Thus XDR padding is not needed in a Write chunk. With NFSv4, the Linux NFS server places the results of any operations that follow an NFSv4 READ or READLINK in the xdr_buf's tail. Those results also should never be sent as a part of a Write chunk. The current logic in send_write_chunks() appears to assume that the xdr_buf's tail contains only pad bytes (ie, NFSv3). The server should write only the contents of the xdr_buf's page list in a Write chunk. If there's more than an XDR pad in the tail, that needs to go inline or in the Reply chunk. BugLink: https://bugzilla.linux-nfs.org/show_bug.cgi?id=294 Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: J. Bruce Fields <bfields@redhat.com> |
||
|---|---|---|
| .. | ||
| backchannel.c | ||
| fmr_ops.c | ||
| frwr_ops.c | ||
| Makefile | ||
| module.c | ||
| physical_ops.c | ||
| rpc_rdma.c | ||
| svc_rdma.c | ||
| svc_rdma_backchannel.c | ||
| svc_rdma_marshal.c | ||
| svc_rdma_recvfrom.c | ||
| svc_rdma_sendto.c | ||
| svc_rdma_transport.c | ||
| transport.c | ||
| verbs.c | ||
| xprt_rdma.h | ||