Linux NFS development
 help / color / mirror / Atom feed
From: Kinglong Mee <kinglongmee@gmail.com>
To: Avi Kivity <avi@cloudius-systems.com>,
	linux-nfs@vger.kernel.org,
	"J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: [PATCH] nfs: fix nfs4d readlink truncated packet
Date: Wed, 02 Jul 2014 16:40:15 +0800	[thread overview]
Message-ID: <53B3C56F.20406@gmail.com> (raw)
In-Reply-To: <53B2999C.6090401@cloudius-systems.com>


On 7/1/2014 19:21, Avi Kivity wrote:
> 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.

Yes, I got
[root@localhost ~]# ll /mnt/
ls: cannot read symbolic link /mnt/test: Input/output error
total 4
-rw-r--r--. 1 root root  0 Jun 14 01:21 123456
lrwxrwxrwx. 1 root root  6 Jul  2 03:33 test
drwxr-xr-x. 1 root root  0 Jul  2 23:50 tmp
drwxr-xr-x. 1 root root 60 Jul  2 23:44 tree
[root@localhost ~]# 

It's introduced by commit 476a7b1f4b2c (nfsd4: don't treat readlink like a zero-copy operation).

> 
>> 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));

NFSD uses (XDR_QUADLEN(maxcount) << 2)) usually.
Anyway, it's a nice fix.

Reviewed-by: Kinglong Mee <kinglongmee@gmail.com>

thanks,
Kinglong Mee

  reply	other threads:[~2014-07-02  8:40 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
2014-07-02  8:40   ` Kinglong Mee [this message]
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=53B3C56F.20406@gmail.com \
    --to=kinglongmee@gmail.com \
    --cc=avi@cloudius-systems.com \
    --cc=bfields@fieldses.org \
    --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