From: Bryan Schumaker <bjschuma@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: trond.myklebust@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/2] NFS: NFSv4 readdir loses entries
Date: Fri, 28 Jan 2011 13:42:02 -0500 [thread overview]
Message-ID: <4D430DFA.90708@netapp.com> (raw)
In-Reply-To: <20110128174105.3235.21014.stgit@matisse.1015granger.net>
On 01/28/2011 12:41 PM, Chuck Lever wrote:
> On recent 2.6.38-rc kernels, connectathon basic test 6 fails on
> NFSv4 mounts of OpenSolaris with something like:
>
>> ./test6: readdir
>> ./test6: (/mnt/klimt/matisse.test) didn't read expected 'file.12' dir entry, pass 0
>> ./test6: (/mnt/klimt/matisse.test) didn't read expected 'file.82' dir entry, pass 0
>> ./test6: (/mnt/klimt/matisse.test) didn't read expected 'file.164' dir entry, pass 0
>> ./test6: (/mnt/klimt/matisse.test) Test failed with 3 errors
>> basic tests failed
>> Tests failed, leaving /mnt/klimt mounted
>> [cel@matisse cthon04]$
>
> I narrowed the problem down to nfs4_decode_direct() reporting that the
I'm guessing that should be nfs4_decode_dirent()?
> decode buffer had overflowed while decoding the entries for those
> missing files.
>
> verify_attr_len() assumes both it's pointer arguments reside on the
> same page. When these arguments point to locations on two different
> pages, verify_attr_len() can report false errors. This can happen now
> that a large NFSv4 readdir result can span pages.
>
> We have reasonably good checking in nfs4_decode_dirent() anyway, so
> it should be safe to simply remove the extra checking.
>
> At a guess, this was introduced by commit 6650239a, "NFS: Don't use
> vm_map_ram() in readdir".
>
> Cc: stable@kernel.org [2.6.37]
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>
> fs/nfs/nfs4xdr.c | 3 ---
> 1 files changed, 0 insertions(+), 3 deletions(-)
>
> diff --git a/fs/nfs/nfs4xdr.c b/fs/nfs/nfs4xdr.c
> index 009aef9..4e2c168 100644
> --- a/fs/nfs/nfs4xdr.c
> +++ b/fs/nfs/nfs4xdr.c
> @@ -6132,9 +6132,6 @@ int nfs4_decode_dirent(struct xdr_stream *xdr, struct nfs_entry *entry,
> if (entry->fattr->valid & NFS_ATTR_FATTR_TYPE)
> entry->d_type = nfs_umode_to_dtype(entry->fattr->mode);
>
> - if (verify_attr_len(xdr, p, len) < 0)
> - goto out_overflow;
> -
> return 0;
>
> out_overflow:
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-28 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 17:40 [PATCH 0/2] Fix Cthon basic test 6 failure Chuck Lever
2011-01-28 17:40 ` [PATCH 1/2] NFS: Micro-optimize nfs4_decode_dirent() Chuck Lever
2011-01-28 17:41 ` [PATCH 2/2] NFS: NFSv4 readdir loses entries Chuck Lever
[not found] ` <20110128174105.3235.21014.stgit-RytpoXr2tKZ9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2011-01-28 18:34 ` Trond Myklebust
[not found] ` <1296239682.5464.15.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2011-01-28 18:39 ` Trond Myklebust
2011-01-28 18:42 ` Bryan Schumaker [this message]
2011-01-28 18:45 ` Trond Myklebust
2011-01-28 19:09 ` Chuck Lever
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=4D430DFA.90708@netapp.com \
--to=bjschuma@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@netapp.com \
/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;
as well as URLs for NNTP newsgroup(s).