From: Avi Kivity <avi@cloudius-systems.com>
To: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs: fix nfs4d readlink truncated packet
Date: Tue, 01 Jul 2014 14:21:00 +0300 [thread overview]
Message-ID: <53B2999C.6090401@cloudius-systems.com> (raw)
In-Reply-To: <1403792592-1517-1-git-send-email-avi@cloudius-systems.com>
On 06/26/2014 05:23 PM, Avi Kivity wrote:
> XDR requires 4-byte alignment; nfs4d READLINK reply writes out the padding,
> but truncates the packet to the padding-less size.
>
> Fix by taking the padding into consideration when truncating the packet.
>
Ping. I should have mentioned that without this, readlink() returns an
I/O error on the client.
> Signed-off-by: Avi Kivity <avi@cloudius-systems.com>
> ---
> fs/nfsd/nfs4xdr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/nfsd/nfs4xdr.c b/fs/nfsd/nfs4xdr.c
> index 83baf2b..cba93ea 100644
> --- a/fs/nfsd/nfs4xdr.c
> +++ b/fs/nfsd/nfs4xdr.c
> @@ -3267,7 +3267,7 @@ nfsd4_encode_readlink(struct nfsd4_compoundres *resp, __be32 nfserr, struct nfsd
>
> wire_count = htonl(maxcount);
> write_bytes_to_xdr_buf(xdr->buf, length_offset, &wire_count, 4);
> - xdr_truncate_encode(xdr, length_offset + 4 + maxcount);
> + xdr_truncate_encode(xdr, length_offset + 4 + ALIGN(maxcount, 4));
> if (maxcount & 3)
> write_bytes_to_xdr_buf(xdr->buf, length_offset + 4 + maxcount,
> &zero, 4 - (maxcount&3));
next prev parent reply other threads:[~2014-07-01 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 14:23 [PATCH] nfs: fix nfs4d readlink truncated packet Avi Kivity
2014-07-01 11:21 ` Avi Kivity [this message]
2014-07-02 8:40 ` Kinglong Mee
2014-07-02 21:42 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53B2999C.6090401@cloudius-systems.com \
--to=avi@cloudius-systems.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox