NFSv4: Fix the alignment of page data in the getdeviceinfo reply
Subsystems (2)
[email protected]
maintainerPATCH 1/3 NFSv4: Fix the alignment of page data in the getdeviceinfo reply
From: Trond Myklebust <[email protected]>
We can fit the device_addr4 opaque data padding in the pages.
--- fs/nfs/nfs4xdr.c | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-)
fs/nfs/nfs4xdr.c +10 -4
@@ -3009,15 +3009,19 @@ static void nfs4_xdr_enc_getdeviceinfo(struct rpc_rqst *req,struct compound_hdr hdr = { .minorversion =nfs4_xdr_minorversion (&args->seq_args), }; +uint32_t replen;encode_compound_hdr (xdr, req, &hdr);encode_sequence (xdr, &args->seq_args, &hdr); + + replen = hdr.replen + op_decode_hdr_maxsz; +encode_getdeviceinfo (xdr, args, &hdr); -/* set up reply kvec. Subtract notification bitmap max size (2) -* so that notification bitmap is put in xdr_buf tail */ +/* set up reply kvec. device_addr4 opaque data is read into the +* pages */ rpc_prepare_reply_pages (req, args->pdev->pages, args->pdev->pgbase, - args->pdev->pglen, hdr.replen -2 ); + args->pdev->pglen, replen +2 );encode_nops (&hdr); }
@@ -5848,7 +5852,9 @@ static int decode_getdeviceinfo(struct xdr_stream *xdr,* and places the remaining xdr data in xdr_buf->tail */ pdev->mincount =be32_to_cpup (p); -if (xdr_read_pages (xdr, pdev->mincount) != pdev->mincount) +/* Calculate padding */ + len =xdr_align_size (pdev->mincount); +if (xdr_read_pages (xdr, len) != len)return -EIO ;/* Parse notification bitmap, verifying that it is zero. */
Signature · 1 line
2.28.0
[email protected]
maintainerPATCH 2/3 NFS: Avoid copy of xdr padding in readlink, layoutget and getxattr
From: Trond Myklebust <[email protected]>
When doing a readlink, layoutget or getxattr call into an array of pages, we don't care if the XDR padding ends up in the last page when the data length is not 32-bit aligned.
Avoid an unnecessary copy by just leaving that padding in place.
--- fs/nfs/nfs2xdr.c | 2 +- fs/nfs/nfs3xdr.c | 2 +- fs/nfs/nfs42xdr.c | 2 +- fs/nfs/nfs4xdr.c | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-)
fs/nfs/nfs2xdr.c +1 -1
@@ -437,7 +437,7 @@ static int decode_path(struct xdr_stream *xdr) length =be32_to_cpup (p);if (unlikely (length >= xdr->buf->page_len || length >NFS_MAXPATHLEN )) goto out_size; - recvd =xdr_read_pages (xdr, length); + recvd =xdr_read_pages (xdr,xdr_align_size (length));if (unlikely (length > recvd)) goto out_cheating;xdr_terminate_string (xdr->buf, length);
fs/nfs/nfs3xdr.c +1 -1
@@ -234,7 +234,7 @@ static int decode_nfspath3(struct xdr_stream *xdr) count =be32_to_cpup (p);if (unlikely (count >= xdr->buf->page_len || count >NFS3_MAXPATHLEN )) goto out_nametoolong; - recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (unlikely (count > recvd)) goto out_cheating;xdr_terminate_string (xdr->buf, count);
fs/nfs/nfs42xdr.c +1 -1
@@ -495,7 +495,7 @@ static int decode_getxattr(struct xdr_stream *xdr, res->xattr_len = len;if (len >0 ) { - rdlen =xdr_read_pages (xdr, len); + rdlen =xdr_read_pages (xdr,xdr_align_size (len));if (rdlen < len)return -EIO ; }
fs/nfs/nfs4xdr.c +2 -2
@@ -5250,7 +5250,7 @@ static int decode_readlink(struct xdr_stream *xdr, struct rpc_rqst *req)dprintk ("nfs: server returned giant symlink!\n" );return -ENAMETOOLONG ; } - recvd =xdr_read_pages (xdr, len); + recvd =xdr_read_pages (xdr,xdr_align_size (len));if (recvd < len) {dprintk ("NFS: server cheating in readlink reply: " "count %u > recvd %u\n" , len, recvd);
@@ -5925,7 +5925,7 @@ static int decode_layoutget(struct xdr_stream *xdr, struct rpc_rqst *req, res->type, res->layoutp->len); - recvd =xdr_read_pages (xdr, res->layoutp->len); + recvd =xdr_read_pages (xdr,xdr_align_size (res->layoutp->len));if (res->layoutp->len > recvd) { dprintk("NFS: server cheating in layoutget reply: " "layout len %u > recvd %u\n",
Signature · 1 line
2.28.0
[email protected]
maintainerPATCH 3/3 NFS: Avoid copy of xdr padding in read()
From: Trond Myklebust <[email protected]>
When doing a read() into a page, we also don't care if the nul padding stays in that last page when the data length is not 32-bit aligned.
--- fs/nfs/nfs2xdr.c | 2 +- fs/nfs/nfs3xdr.c | 2 +- fs/nfs/nfs4xdr.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
fs/nfs/nfs2xdr.c +1 -1
@@ -102,7 +102,7 @@ static int decode_nfsdata(struct xdr_stream *xdr, struct nfs_pgio_res *result)if (unlikely (!p))return -EIO ; count =be32_to_cpup (p); - recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (unlikely (count > recvd)) goto out_cheating; out:
fs/nfs/nfs3xdr.c +1 -1
@@ -1611,7 +1611,7 @@ static int decode_read3resok(struct xdr_stream *xdr, ocount =be32_to_cpup (p++);if (unlikely (ocount != count)) goto out_mismatch; - recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (unlikely (count > recvd)) goto out_cheating; out:
fs/nfs/nfs4xdr.c +1 -1
@@ -5202,7 +5202,7 @@ static int decode_read(struct xdr_stream *xdr, struct rpc_rqst *req,return -EIO ; eof =be32_to_cpup (p++); count =be32_to_cpup (p); - recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (count > recvd) {dprintk ("NFS: server cheating in read reply: " "count %u > recvd %u\n" , count, recvd);
Signature · 1 line
2.28.0
Re: [PATCH 3/3] NFS: Avoid copy of xdr padding in read()
Quoted 8 lines · On Nov 18, 2020, at 5:19 PM, [email protected] wrote:
From: Trond Myklebust <[email protected]>
When doing a
read()into a page, we also don't care if the nul padding stays in that last page when the data length is not 32-bit aligned.
What if the READ payload lands in the middle of a file? The pad on the end will overwrite file content just past where the READ payload lands.
Quoted 49 lines
Signed-off-by Trond Myklebust <[email protected]>---
fs/nfs/nfs2xdr.c | 2 +- fs/nfs/nfs3xdr.c | 2 +- fs/nfs/nfs4xdr.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)fs/nfs/nfs2xdr.c +1
-1@@ -102,7 +102,7 @@ static int decode_nfsdata(struct xdr_stream *xdr, struct nfs_pgio_res *result)if (unlikely (!p))return -EIO ; count =be32_to_cpup (p); - recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (unlikely (count > recvd)) goto out_cheating;out:
fs/nfs/nfs3xdr.c +1
-1@@ -1611,7 +1611,7 @@ static int decode_read3resok(struct xdr_stream *xdr, ocount =be32_to_cpup (p++);if (unlikely (ocount != count)) goto out_mismatch; - recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (unlikely (count > recvd)) goto out_cheating;out:
fs/nfs/nfs4xdr.c +1
-1@@ -5202,7 +5202,7 @@ static int decode_read(struct xdr_stream *xdr, struct rpc_rqst *req,return -EIO ; eof =be32_to_cpup (p++); count =be32_to_cpup (p); - recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (count > recvd) {dprintk ("NFS: server cheating in read reply: " "count %u > recvd %u\n" , count, recvd);Signature · 1 line
2.28.0
--
Chuck Lever
Re: [PATCH 3/3] NFS: Avoid copy of xdr padding in read()
Quoted 6 lines · Chuck Lever
Quoted 6 lines · On Nov 18, 2020, at 5:19 PM, [email protected] wrote:
From: Trond Myklebust <[email protected]>
Quoted 7 lines
Quoted 3 lines
When doing a
read()into a page, we also don't care if the nul padding
stays in that last page when the data length is not 32-bit aligned.What if the READ payload lands in the middle of a file? The pad on the end will overwrite file content just past where the READ payload lands.
If the size > buf->page_len, then it gets truncated in xdr_align_pages() afaik.
Quoted 61 lines
Quoted 49 lines
Signed-off-by Trond Myklebust <[email protected]>---
fs/nfs/nfs2xdr.c | 2 +- fs/nfs/nfs3xdr.c | 2 +- fs/nfs/nfs4xdr.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)fs/nfs/nfs2xdr.c +1
-1@@ -102,7 +102,7 @@ static int decode_nfsdata(struct xdr_stream *xdr, struct nfs_pgio_res *result) if (unlikely(!p)) return -EIO; count = be32_to_cpup(p); - recvd = xdr_read_pages(xdr, count); + recvd = xdr_read_pages(xdr, xdr_align_size(count)); if (unlikely(count > recvd)) goto out_cheating;out:
fs/nfs/nfs3xdr.c +1
-1@@ -1611,7 +1611,7 @@ static int decode_read3resok(structxdr_stream *xdr, ocount = be32_to_cpup(p++); if (unlikely(ocount != count)) goto out_mismatch; - recvd = xdr_read_pages(xdr, count); + recvd = xdr_read_pages(xdr, xdr_align_size(count)); if (unlikely(count > recvd)) goto out_cheating;out:
fs/nfs/nfs4xdr.c +1
-1@@ -5202,7 +5202,7 @@ static int decode_read(struct xdr_stream *xdr, struct rpc_rqst *req, return -EIO; eof = be32_to_cpup(p++); count = be32_to_cpup(p); - recvd = xdr_read_pages(xdr, count); + recvd = xdr_read_pages(xdr, xdr_align_size(count)); if (count > recvd) {Quoted 6 lines
dprintk("NFS: server cheating in read reply: " "count %u > recvd %u\n", count, recvd);
Signature · 1 line
2.28.0--
Chuck Lever
Signature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]
Re: [PATCH 3/3] NFS: Avoid copy of xdr padding in read()
Quoted 15 lines · Trond Myklebust
Quoted 10 lines · Chuck Lever
Quoted 9 lines · On Nov 18, 2020, at 5:19 PM, [email protected] wrote:
From: Trond Myklebust <[email protected]>
When doing a
read()into a page, we also don't care if the nul padding
stays in that last page when the data length is not 32-bit aligned.
Quoted 6 lines
Quoted 3 lines
What if the READ payload lands in the middle of a file? The pad on the end will overwrite file content just past where the READ payload lands.
If the size >
buf->page_len, then it gets truncated inxdr_align_pages()afaik.
I will need to check how RPC/RDMA behaves. It might build a chunk that includes the pad in this case, which would break things.
Quoted 51 lines
Quoted 51 lines
Quoted 51 lines
Signed-off-by Trond Myklebust <[email protected]>---
fs/nfs/nfs2xdr.c | 2 +- fs/nfs/nfs3xdr.c | 2 +- fs/nfs/nfs4xdr.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)fs/nfs/nfs2xdr.c +1
-1@@ -102,7 +102,7 @@ static int decode_nfsdata(struct xdr_stream *xdr, struct nfs_pgio_res *result)if (unlikely (!p))return -EIO ; count =be32_to_cpup (p); - recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (unlikely (count > recvd)) goto out_cheating;out:
fs/nfs/nfs3xdr.c +1
-1@@ -1611,7 +1611,7 @@ static int decode_read3resok(structxdr_stream *xdr, ocount =be32_to_cpup (p++);if (unlikely (ocount != count)) goto out_mismatch; - recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (unlikely (count > recvd)) goto out_cheating;out:
fs/nfs/nfs4xdr.c +1
-1@@ -5202,7 +5202,7 @@ static int decode_read(struct xdr_stream *xdr, struct rpc_rqst *req, return -EIO ; eof =be32_to_cpup (p++); count =be32_to_cpup (p); - recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (count > recvd) { dprintk("NFS: server cheating in read reply: ""count %u > recvd %u\n", count,recvd);
Quoted 13 lines
Quoted 8 lines
Quoted 2 lines
2.28.0
--
Chuck LeverSignature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]
--
Chuck Lever
Re: [PATCH 3/3] NFS: Avoid copy of xdr padding in read()
Quoted 21 lines · Chuck Lever
Quoted 21 lines
On Nov 19, 2020, at 9:30 AM, Trond Myklebust <
[email protected]> wrote:Quoted 14 lines · Chuck Lever
Quoted 10 lines · On Nov 18, 2020, at 5:19 PM, [email protected] wrote:
From: Trond Myklebust <[email protected]>
When doing a
read()into a page, we also don't care if the nul padding
stays in that last page when the data length is not 32-bit aligned.What if the READ payload lands in the middle of a file? The pad on the end will overwrite file content just past where the READ payload lands.
Quoted 6 lines
Quoted 2 lines
If the size >
buf->page_len, then it gets truncated inxdr_align_pages()afaik.I will need to check how RPC/RDMA behaves. It might build a chunk that includes the pad in this case, which would break things.
That would be a bug in the existing code too, then. It shouldn't be writing beyond the buffer size we set in the NFS layer.
Quoted 53 lines
Quoted 53 lines
Quoted 53 lines
Quoted 53 lines
Signed-off-by: Trond Myklebust
<[email protected]>
---fs/nfs/nfs2xdr.c | 2 +- fs/nfs/nfs3xdr.c | 2 +- fs/nfs/nfs4xdr.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)fs/nfs/nfs2xdr.c +1
-1@@ -102,7 +102,7 @@ static int decode_nfsdata(struct xdr_stream *xdr, struct nfs_pgio_res *result) if (unlikely(!p)) return -EIO; count = be32_to_cpup(p); - recvd = xdr_read_pages(xdr, count); + recvd = xdr_read_pages(xdr, xdr_align_size(count)); if (unlikely(count > recvd)) goto out_cheating;out:
fs/nfs/nfs3xdr.c +1
-1@@ -1611,7 +1611,7 @@ static int decode_read3resok(structxdr_stream *xdr, ocount = be32_to_cpup(p++); if (unlikely(ocount != count)) goto out_mismatch; - recvd = xdr_read_pages(xdr, count); + recvd = xdr_read_pages(xdr, xdr_align_size(count)); if (unlikely(count > recvd)) goto out_cheating;out:
fs/nfs/nfs4xdr.c +1
-1@@ -5202,7 +5202,7 @@ static int decode_read(struct xdr_stream *xdr, struct rpc_rqst *req, return -EIO; eof = be32_to_cpup(p++); count = be32_to_cpup(p); - recvd = xdr_read_pages(xdr, count); + recvd = xdr_read_pages(xdr, xdr_align_size(count)); if (count > recvd) {
dprintk("NFS: server cheating in read reply: " "count %u > recvd %u\n", count, recvd);Signature · 1 line
2.28.0
Signature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]
Re: [PATCH 3/3] NFS: Avoid copy of xdr padding in read()
Quoted 29 lines · Trond Myklebust
Quoted 24 lines · Chuck Lever
Quoted 23 lines
On Nov 19, 2020, at 9:30 AM, Trond Myklebust <
[email protected]> wrote:Quoted 6 lines · Chuck Lever
Quoted 6 lines · On Nov 18, 2020, at 5:19 PM, [email protected] wrote:
From: Trond Myklebust <[email protected]>
Quoted 8 lines
Quoted 4 lines
When doing a
read()into a page, we also don't care if the nul padding
stays in that last page when the data length is not 32-bit aligned.What if the READ payload lands in the middle of a file? The pad on the end will overwrite file content just past where the READ payload lands.
If the size >
buf->page_len, then it gets truncated inxdr_align_pages()afaik.
Quoted 6 lines
Quoted 3 lines
I will need to check how RPC/RDMA behaves. It might build a chunk that includes the pad in this case, which would break things.
That would be a bug in the existing code too, then. It shouldn't be writing beyond the buffer size we set in the NFS layer.
Testing now with xfstests, which should include fsx with direct I/O of odd sizes. So far I haven't seen any unexpected behavior.
But I'm not sure what copy you're trying to avoid. This one in xdr_align_pages() ?
1189 else if (nwords < xdr->nwords) {
1190 /* Truncate page data and move it into the tail */ 1191 offset = buf->page_len - len; 1192 copied = xdr_shrink_pagelen(buf, offset); 1193 trace_rpc_xdr_alignment(xdr, offset, copied); 1194 xdr->nwords = XDR_QUADLEN(buf->len - cur);
1195 }
We set up the receive buffer already to avoid this copy. It should rarely, if ever, happen. That's the point of rpc_prepare_reply_pages().
Quoted 45 lines
Quoted 45 lines
Quoted 45 lines
Quoted 45 lines
Quoted 45 lines
Signed-off-by: Trond Myklebust
<[email protected]>
---fs/nfs/nfs2xdr.c | 2 +- fs/nfs/nfs3xdr.c | 2 +- fs/nfs/nfs4xdr.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)fs/nfs/nfs2xdr.c +1
-1@@ -102,7 +102,7 @@ static int decode_nfsdata(struct xdr_stream *xdr, struct nfs_pgio_res *result)if (unlikely (!p))return -EIO ; count =be32_to_cpup (p); - recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (unlikely (count > recvd)) goto out_cheating;out:
fs/nfs/nfs3xdr.c +1
-1@@ -1611,7 +1611,7 @@ static int decode_read3resok(structxdr_stream *xdr, ocount =be32_to_cpup (p++);if (unlikely (ocount != count)) goto out_mismatch; - recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (unlikely (count > recvd)) goto out_cheating;out:
fs/nfs/nfs4xdr.c +0
-0@@ -5202,7 +5202,7 @@ static int decode_read(struct xdr_stream *xdr, struct rpc_rqst *req, return -EIO ; eof =be32_to_cpup (p++); count =be32_to_cpup (p);
Quoted 15 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
fs/nfs/nfs4xdr.c +1
-1- recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (count > recvd) { dprintk("NFS: server cheating in read reply: ""count %u > recvd %u\n", count,recvd);
Signature · 1 line
2.28.0Signature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]
--
Chuck Lever
Re: [PATCH 3/3] NFS: Avoid copy of xdr padding in read()
Quoted 53 lines · Chuck Lever
Quoted 31 lines
On Nov 19, 2020, at 9:34 AM, Trond Myklebust <
[email protected]> wrote:Quoted 25 lines · Chuck Lever
Quoted 24 lines
On Nov 19, 2020, at 9:30 AM, Trond Myklebust <
[email protected]> wrote:Quoted 12 lines · Chuck Lever
Quoted 11 lines · On Nov 18, 2020, at 5:19 PM, [email protected] wrote:
From: Trond Myklebust <[email protected]>
When doing a
read()into a page, we also don't care if the nul
padding
stays in that last page when the data length is not 32-bit aligned.Quoted 3 lines
What if the READ payload lands in the middle of a file? The pad on the end will overwrite file content just past where the READ payload lands.
If the size >
buf->page_len, then it gets truncated inxdr_align_pages()afaik.Quoted 6 lines
Quoted 3 lines
I will need to check how RPC/RDMA behaves. It might build a chunk that includes the pad in this case, which would break things.
That would be a bug in the existing code too, then. It shouldn't be writing beyond the buffer size we set in the NFS layer.
Testing now with xfstests, which should include fsx with direct I/O of odd sizes. So far I haven't seen any unexpected behavior.
But I'm not sure what copy you're trying to avoid. This one in
xdr_align_pages()?1189 else if (nwords <
xdr->nwords) {
1190 /* Truncate page data and move it into the tail */
1191 offset =buf->page_len- len;
1192 copied =xdr_shrink_pagelen(buf, offset); 1193trace_rpc_xdr_alignment(xdr, offset, copied); 1194xdr->nwords=XDR_QUADLEN(buf->len - cur); 1195 }
Quoted 3 lines
We set up the receive buffer already to avoid this copy. It should rarely, if ever, happen. That's the point of
rpc_prepare_reply_pages().
...and the point of padding here is to avoid unaligned access to memory. That is completely broken by this whole mechanism, which causes us to place the real data in the tail in an unaligned buffer that follows this padding.
Furthermore, rpc_prepare_reply_pages() only ever places the padding in the tail _if_ our buffer size is already not 32-bit aligned. Otherwise, we're engaging in this pointless exercise of making the tail buffer data unaligned after the fact.
Quoted 71 lines
Quoted 50 lines
Quoted 50 lines
Quoted 50 lines
Quoted 50 lines
Quoted 50 lines
Signed-off-by: Trond Myklebust
<[email protected]>
---fs/nfs/nfs2xdr.c | 2 +- fs/nfs/nfs3xdr.c | 2 +- fs/nfs/nfs4xdr.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)fs/nfs/nfs2xdr.c +0
-0@@ -102,7 +102,7 @@ static int decode_nfsdata(struct
xdr_stream
*xdr, structnfs_pgio_res*result)
if (unlikely(!p))
return-EIO;
count =be32_to_cpup(p);
- recvd =xdr_read_pages(xdr, count);
+ recvd =xdr_read_pages(xdr, xdr_align_size(count)); if (unlikely(count > recvd))
gotoout_cheating;
out:fs/nfs/nfs3xdr.c +1
-1@@ -1611,7 +1611,7 @@ static int decode_read3resok(structxdr_stream *xdr, ocount = be32_to_cpup(p++); if (unlikely(ocount != count)) goto out_mismatch; - recvd = xdr_read_pages(xdr, count); + recvd = xdr_read_pages(xdr, xdr_align_size(count)); if (unlikely(count > recvd)) goto out_cheating;out:
fs/nfs/nfs4xdr.c +0
-0@@ -5202,7 +5202,7 @@ static int decode_read(struct
xdr_stream
*xdr, structrpc_rqst*req,
return-EIO;
eof =be32_to_cpup(p++);
count =be32_to_cpup(p);
- recvd =xdr_read_pages(xdr, count);
+ recvd =xdr_read_pages(xdr, xdr_align_size(count));Quoted 15 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
if (count > recvd) {
dprintk("NFS: server cheating in read
reply: "
"count %u > recvd %u\n", count,
recvd);Signature · 1 line
2.28.0Signature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]--
Chuck Lever
Signature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]
Re: [PATCH 3/3] NFS: Avoid copy of xdr padding in read()
Quoted 63 lines · Trond Myklebust
Quoted 51 lines · Chuck Lever
Quoted 31 lines
On Nov 19, 2020, at 9:34 AM, Trond Myklebust <
[email protected]> wrote:Quoted 25 lines · Chuck Lever
Quoted 24 lines
On Nov 19, 2020, at 9:30 AM, Trond Myklebust <
[email protected]> wrote:Quoted 12 lines · Chuck Lever
Quoted 11 lines · On Nov 18, 2020, at 5:19 PM, [email protected] wrote:
From: Trond Myklebust <[email protected]>
When doing a
read()into a page, we also don't care if the nul
padding
stays in that last page when the data length is not 32-bit aligned.Quoted 3 lines
What if the READ payload lands in the middle of a file? The pad on the end will overwrite file content just past where the READ payload lands.
If the size >
buf->page_len, then it gets truncated inxdr_align_pages()afaik.Quoted 6 lines
Quoted 3 lines
I will need to check how RPC/RDMA behaves. It might build a chunk that includes the pad in this case, which would break things.
That would be a bug in the existing code too, then. It shouldn't be writing beyond the buffer size we set in the NFS layer.
Testing now with xfstests, which should include fsx with direct I/O of odd sizes. So far I haven't seen any unexpected behavior.
But I'm not sure what copy you're trying to avoid. This one in
xdr_align_pages()?1189 else if (nwords <
xdr->nwords) {
1190 /* Truncate page data and move it into the tail
*/1191 offset = buf->page_len - len; 1192 copied = xdr_shrink_pagelen(buf, offset); 1193 trace_rpc_xdr_alignment(xdr, offset, copied); 1194 xdr->nwords = XDR_QUADLEN(buf->len - cur);Quoted 5 lines
1195 }
We set up the receive buffer already to avoid this copy. It should rarely, if ever, happen. That's the point of
rpc_prepare_reply_pages().
Quoted 4 lines
...and the point of padding here is to avoid unaligned access to memory. That is completely broken by this whole mechanism, which causes us to place the real data in the tail in an unaligned buffer that follows this padding.
I've never seen run-time complaints about unaligned accesses of the tail data. Do you have a reproducer? (And obviously this applies only to NFSv4 COMPOUND results, right?)
Quoted 4 lines
Furthermore,
rpc_prepare_reply_pages()only ever places the padding in the tail _if_ our buffer size is already not 32-bit aligned. Otherwise, we're engaging in this pointless exercise of making the tail buffer data unaligned after the fact.
Architecturally, I agree that it would be best if the tail buffer presented the XDR data items aligned on 4 bytes.
But I do not agree that a pad goes in the pages. Some transports do not send an XDR pad for unaligned data payloads. Transports have to have a way of avoiding that pad. If it no longer goes in the tail, then how will they do that?
We could perhaps have a new flag, XDRBUF_IMPLICIT_PAD, that means the transport has to add a pad to xdr->pages on send, or did not add a pad on receive.
Quoted 65 lines
Quoted 65 lines
Quoted 64 lines
Quoted 57 lines
Quoted 57 lines
Quoted 57 lines
Quoted 57 lines
Signed-off-by: Trond Myklebust
<[email protected]>
---fs/nfs/nfs2xdr.c | 2 +- fs/nfs/nfs3xdr.c | 2 +- fs/nfs/nfs4xdr.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)fs/nfs/nfs2xdr.c +0
-0@@ -102,7 +102,7 @@ static int decode_nfsdata(struct
xdr_stream
*xdr, structnfs_pgio_res*result)if (unlikely(!p)) return -EIO; count = be32_to_cpup(p);fs/nfs/nfs2xdr.c +1
-1- recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (unlikely (count > recvd)) goto out_cheating;out:
fs/nfs/nfs3xdr.c +1
-1@@ -1611,7 +1611,7 @@ static int decode_read3resok(structxdr_stream *xdr, ocount =be32_to_cpup (p++);if (unlikely (ocount != count)) goto out_mismatch; - recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (unlikely (count > recvd)) goto out_cheating;out:
fs/nfs/nfs4xdr.c +0
-0@@ -5202,7 +5202,7 @@ static int decode_read(struct
xdr_stream
*xdr, structrpc_rqst*req,return -EIO; eof = be32_to_cpup(p++); count = be32_to_cpup(p);fs/nfs/nfs4xdr.c +1
-1- recvd =xdr_read_pages (xdr, count); + recvd =xdr_read_pages (xdr,xdr_align_size (count));if (count > recvd) { dprintk("NFS: server cheating in readreply: "
"count %u > recvd %u\n",count,
recvd);Signature · 1 line
2.28.0Signature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]
Quoted 10 lines
Quoted 5 lines
--
Chuck LeverSignature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]
--
Chuck Lever
Re: [PATCH 3/3] NFS: Avoid copy of xdr padding in read()
Quoted 78 lines · Chuck Lever
Quoted 72 lines
On Nov 19, 2020, at 7:58 PM, Trond Myklebust <
[email protected]> wrote:Quoted 60 lines · Chuck Lever
Quoted 35 lines
On Nov 19, 2020, at 9:34 AM, Trond Myklebust <
[email protected]> wrote:Quoted 29 lines · Chuck Lever
Quoted 28 lines
On Nov 19, 2020, at 9:30 AM, Trond Myklebust <
[email protected]> wrote:Quoted 14 lines · Chuck Lever
Quoted 13 lines · On Nov 18, 2020, at 5:19 PM, [email protected] wrote:
From: Trond Myklebust <[email protected]>
When doing a
read()into a page, we also don't care if the
nul
padding
stays in that last page when the data length is not 32- bit
aligned.Quoted 5 lines
What if the READ payload lands in the middle of a file? The
pad on the end will overwrite file content just past where
the READ payload lands.If the size >
buf->page_len, then it gets truncated inxdr_align_pages()afaik.Quoted 7 lines
Quoted 3 lines
I will need to check how RPC/RDMA behaves. It might build a chunk that includes the pad in this case, which would break things.
That would be a bug in the existing code too, then. It shouldn't be
writing beyond the buffer size we set in the NFS layer.Testing now with xfstests, which should include fsx with direct I/O of odd sizes. So far I haven't seen any unexpected behavior.
But I'm not sure what copy you're trying to avoid. This one in
xdr_align_pages()?1189 else if (nwords <
xdr->nwords) {
1190 /* Truncate page data and move it into the tail
*/
1191 offset =buf->page_len- len; 1192 copied =xdr_shrink_pagelen(buf, offset); 1193trace_rpc_xdr_alignment(xdr, offset, copied);
1194xdr->nwords=XDR_QUADLEN(buf->len - cur); 1195 }Quoted 4 lines
We set up the receive buffer already to avoid this copy. It should
rarely, if ever, happen. That's the point ofrpc_prepare_reply_pages().Quoted 5 lines
...and the point of padding here is to avoid unaligned access to memory. That is completely broken by this whole mechanism, which causes
us to place the real data in the tail in an unaligned buffer that follows this padding.
Quoted 3 lines
I've never seen run-time complaints about unaligned accesses of the tail data. Do you have a reproducer? (And obviously this applies only to NFSv4 COMPOUND results, right?)
I don't think we can trigger it anywhere right now mainly because we're careful never to put any further ops after a read, readdir or readlink, even though we probably should append a VERIFY to some of those so as to protect data caching (particularly for readlink).
Quoted 11 lines
Quoted 7 lines
Furthermore,
rpc_prepare_reply_pages()only ever places the padding in
the tail _if_ our buffer size is already not 32-bit aligned. Otherwise,
we're engaging in this pointless exercise of making the tail buffer data unaligned after the fact.Architecturally, I agree that it would be best if the tail buffer presented the XDR data items aligned on 4 bytes.
Quoted 9 lines
But I do not agree that a pad goes in the pages. Some transports do not send an XDR pad for unaligned data payloads. Transports have to have a way of avoiding that pad. If it no longer goes in the tail, then how will they do that?
We could perhaps have a new flag,
XDRBUF_IMPLICIT_PAD, that means the transport has to add a pad toxdr->pageson send, or did not add a pad on receive.
I don't see why we would need any of this. If the pad is being directly placed in the tail by the RPC transport layer, then there is nothing in xdr_read_pages() that will move it or change the alignment of the existing code in the tail. The call just notes that xdr_align_pages() returned a length that was shorter than the one we supplied, and continues to skip the padding in the tail.
The one thing that perhaps is broken here is that if we supply a length to xdr_read_pages() that is in fact larger than xdr_align_size(xdr-
Quoted 1 line
buf->page_len), then we should skip additional data that was placed in
the tail, but that is a bug with the existing xdr_read_pages() and is unaffected by these patches.
Quoted 87 lines
Quoted 71 lines
Quoted 71 lines
Quoted 70 lines
Quoted 63 lines
Quoted 63 lines
Quoted 63 lines
Quoted 63 lines
Signed-off-by: Trond Myklebust
<[email protected]>
---fs/nfs/nfs2xdr.c | 2 +- fs/nfs/nfs3xdr.c | 2 +- fs/nfs/nfs4xdr.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)fs/nfs/nfs2xdr.c +0
-0@@ -102,7 +102,7 @@ static int decode_nfsdata(struct
xdr_stream
*xdr, structnfs_pgio_res*result)
if (unlikely(!p))
return-EIO;
count =be32_to_cpup(p);
- recvd =xdr_read_pages(xdr, count);
+ recvd = xdr_read_pages(xdr,xdr_align_size(count));
if (unlikely(count > recvd))
gotoout_cheating;
out:fs/nfs/nfs3xdr.c +0
-0@@ -1611,7 +1611,7 @@ static intdecode_read3resok(struct
xdr_stream*xdr,
ocount =be32_to_cpup(p++);
if (unlikely(ocount != count))
gotoout_mismatch;
- recvd =xdr_read_pages(xdr, count);
+ recvd = xdr_read_pages(xdr,xdr_align_size(count));
if (unlikely(count > recvd))
gotoout_cheating;
out:fs/nfs/nfs4xdr.c +0
-0@@ -5202,7 +5202,7 @@ static int decode_read(struct
xdr_stream
*xdr, structrpc_rqst*req,
return-EIO;
eof =be32_to_cpup(p++);
count =be32_to_cpup(p);
- recvd =xdr_read_pages(xdr, count);
+ recvd =xdr_read_pages(xdr, xdr_align_size(count));
if (count > recvd) {
dprintk("NFS: server cheating in read
reply: "
"count %u > recvd %u\n",
count,
recvd);Signature · 1 line
2.28.0Signature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]Quoted 10 lines
Quoted 5 lines
--
Chuck LeverSignature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]--
Chuck Lever
Signature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]
Re: [PATCH 3/3] NFS: Avoid copy of xdr padding in read()
Quoted 108 lines · Trond Myklebust
Quoted 78 lines · Chuck Lever
Quoted 72 lines
On Nov 19, 2020, at 7:58 PM, Trond Myklebust <
[email protected]> wrote:Quoted 56 lines · Chuck Lever
Quoted 35 lines
On Nov 19, 2020, at 9:34 AM, Trond Myklebust <
[email protected]> wrote:Quoted 29 lines · Chuck Lever
Quoted 28 lines
On Nov 19, 2020, at 9:30 AM, Trond Myklebust <
[email protected]> wrote:Quoted 14 lines · Chuck Lever
Quoted 13 lines · On Nov 18, 2020, at 5:19 PM, [email protected] wrote:
From: Trond Myklebust <[email protected]>
When doing a
read()into a page, we also don't care if the
nul
padding
stays in that last page when the data length is not 32- bit
aligned.Quoted 5 lines
What if the READ payload lands in the middle of a file? The
pad on the end will overwrite file content just past where
the READ payload lands.If the size >
buf->page_len, then it gets truncated inxdr_align_pages()afaik.Quoted 7 lines
Quoted 3 lines
I will need to check how RPC/RDMA behaves. It might build a chunk that includes the pad in this case, which would break things.
That would be a bug in the existing code too, then. It shouldn't be
writing beyond the buffer size we set in the NFS layer.Testing now with xfstests, which should include fsx with direct I/O of odd sizes. So far I haven't seen any unexpected behavior.
But I'm not sure what copy you're trying to avoid. This one in
xdr_align_pages()?1189 else if (nwords <
xdr->nwords) {
1190 /* Truncate page data and move it into the
tail
*/1191 offset = buf->page_len - len; 1192 copied = xdr_shrink_pagelen(buf, offset); 1193 trace_rpc_xdr_alignment(xdr, offset,Quoted 8 lines
copied);
1194xdr->nwords=XDR_QUADLEN(buf->len - cur);
1195 }We set up the receive buffer already to avoid this copy. It should
rarely, if ever, happen. That's the point ofrpc_prepare_reply_pages().Quoted 5 lines
...and the point of padding here is to avoid unaligned access to memory. That is completely broken by this whole mechanism, which causes
us to place the real data in the tail in an unaligned buffer that follows this padding.Quoted 3 lines
I've never seen run-time complaints about unaligned accesses of the tail data. Do you have a reproducer? (And obviously this applies only to NFSv4 COMPOUND results, right?)
I don't think we can trigger it anywhere right now mainly because we're careful never to put any further ops after a read, readdir or readlink, even though we probably should append a VERIFY to some of those so as to protect data caching (particularly for readlink).
Quoted 16 lines
Quoted 7 lines
Furthermore,
rpc_prepare_reply_pages()only ever places the padding in
the tail _if_ our buffer size is already not 32-bit aligned. Otherwise,
we're engaging in this pointless exercise of making the tail buffer data unaligned after the fact.Architecturally, I agree that it would be best if the tail buffer presented the XDR data items aligned on 4 bytes.
But I do not agree that a pad goes in the pages. Some transports do not send an XDR pad for unaligned data payloads. Transports have to have a way of avoiding that pad. If it no longer goes in the tail, then how will they do that?
Quoted 6 lines
Quoted 4 lines
We could perhaps have a new flag,
XDRBUF_IMPLICIT_PAD, that means the transport has to add a pad toxdr->pageson send, or did not add a pad on receive.I don't see why we would need any of this.
Right. I was conflating the send and receive side. You're talking about only receive. This would be a problem when the structure of the reply doesn't allow the client to align the pages and tail[] in advance.
So, READ/READLINK/READDIR/LISTXATTRS, on either TCP, or with RDMA and krb5i and krb5p where XDR pads have to stay inline. I'm still a little troubled by what happens to the pad during a short READ.
The common case for READ requests is page-aligned payloads, so I don't think tail content alignment is a performance issue. Do you concur?
Quoted 6 lines
If the pad is being directly
placed in the tail by the RPC transport layer, then there is nothing inxdr_read_pages()that will move it or change the alignment of the existing code in the tail. The call just notes thatxdr_align_pages()returned a length that was shorter than the one we supplied, and continues to skip the padding in the tail.
That's what I observe today. I'm trying to understand the usage scenario where the tail content is not word-aligned. Probably can happen on server-side receives too.
Quoted 5 lines
The one thing that perhaps is broken here is that if we supply a length to
xdr_read_pages()that is in fact larger than xdr_align_size(xdr-Quoted 1 line
buf->page_len), then we should skip additional data that was placed inthe tail, but that is a bug with the existing
xdr_read_pages()and is unaffected by these patches.
I think I understand what these patches do well enough to drop my objection, pending further exercise with a testing barrage.
Quoted 81 lines
Quoted 81 lines
Quoted 80 lines
Quoted 75 lines
Quoted 54 lines
Quoted 54 lines
Quoted 54 lines
Quoted 54 lines
Quoted 54 lines
Signed-off-by: Trond Myklebust
<[email protected]>
---fs/nfs/nfs2xdr.c | 2 +- fs/nfs/nfs3xdr.c | 2 +- fs/nfs/nfs4xdr.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)fs/nfs/nfs2xdr.c +0
-0@@ -102,7 +102,7 @@ static int decode_nfsdata(struct
xdr_stream
*xdr, structnfs_pgio_res*result)if (unlikely(!p)) return -EIO; count = be32_to_cpup(p);fs/nfs/nfs2xdr.c +1
-1- recvd =xdr_read_pages (xdr, count); + recvd = xdr_read_pages(xdr,
xdr_align_size(count));
if (unlikely(count > recvd))
gotoout_cheating;
out:fs/nfs/nfs3xdr.c +0
-0@@ -1611,7 +1611,7 @@ static intdecode_read3resok(struct
xdr_stream*xdr,ocount = be32_to_cpup(p++); if (unlikely(ocount != count)) goto out_mismatch;fs/nfs/nfs3xdr.c +1
-1- recvd =xdr_read_pages (xdr, count); + recvd = xdr_read_pages(xdr,
xdr_align_size(count));
if (unlikely(count > recvd))
gotoout_cheating;
out:fs/nfs/nfs4xdr.c +0
-0@@ -5202,7 +5202,7 @@ static int decode_read(struct
xdr_stream
*xdr, structrpc_rqst*req,return -EIO; eof = be32_to_cpup(p++); count = be32_to_cpup(p);fs/nfs/nfs4xdr.c +1
-1- recvd =xdr_read_pages (xdr, count); + recvd = xdr_read_pages(xdr,xdr_align_size(count)); if (count > recvd) {Quoted 15 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
dprintk("NFS: server cheating in read
reply: "
"count %u > recvd
%u\n",
count,
recvd);Signature · 1 line
2.28.0Signature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]--
Chuck LeverSignature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]
Quoted 10 lines
Quoted 5 lines
--
Chuck LeverSignature · 3 lines
Trond Myklebust Linux NFS client maintainer, Hammerspace [email protected]
--
Chuck Lever