From: Steven <steven@void.org>
To: Olaf Kirch <okir@suse.de>
Cc: Steven <steven@void.org>, nfs@lists.sourceforge.net
Subject: Re: NFS crash problem in readdirplus
Date: Wed, 20 Apr 2005 11:34:37 -0700 [thread overview]
Message-ID: <20050420183438.10F691165A4@dead.void.org> (raw)
In-Reply-To: Message from Olaf Kirch <okir@suse.de> of "Wed, 20 Apr 2005 10:49:35 +0200." <20050420084935.GA30863@suse.de>
Right, resp->buffer is set here;
int
nfs3svc_decode_readdirplusargs(struct svc_rqst *rqstp, u32 *p,
struct nfsd3_readdirargs *args)
{
int len, pn;
if (!(p = decode_fh(p, &args->fh)))
return 0;
p = xdr_decode_hyper(p, &args->cookie);
args->verf = p; p += 2;
args->dircount = ntohl(*p++);
args->count = ntohl(*p++);
len = (args->count > NFSSVC_MAXBLKSIZE) ? NFSSVC_MAXBLKSIZE :
args->count;
args->count = len;
while (len > 0) {
pn = rqstp->rq_resused;
svc_take_page(rqstp);
if (!args->buffer)
here --> args->buffer = page_address(rqstp->rq_respages[pn]);
len -= PAGE_SIZE;
}
return xdr_argsize_check(rqstp, p);
}
If len == 0 then the conditional on that loop never holds and
args->buffer is never set.
I think that a maxcount of 0 is an invalid argument. The rfc says that
the size must include all XDR overhead so there is no way to reply
successfully when maxcount is 0.
--Steven
-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-04-20 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 17:30 NFS crash problem in readdirplus Steven
2005-04-20 8:49 ` Olaf Kirch
2005-04-20 18:34 ` Steven [this message]
2005-04-20 20:10 ` Trond Myklebust
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=20050420183438.10F691165A4@dead.void.org \
--to=steven@void.org \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
/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