From: Olaf Kirch <okir@suse.de>
To: Steven <steven@void.org>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS crash problem in readdirplus
Date: Wed, 20 Apr 2005 10:49:35 +0200 [thread overview]
Message-ID: <20050420084935.GA30863@suse.de> (raw)
In-Reply-To: <20050401173053.32F551154F4@dead.void.org>
On Fri, Apr 01, 2005 at 09:30:53AM -0800, Steven wrote:
> A readdirplus call with count=0 reliably causes a server crash due to a
> null pointer dereference. The relevant information from my
> /var/log/messages is at the end of this message.
According to your Oops, it dies here:
int
nfs3svc_encode_readdirres(struct svc_rqst *rqstp, u32 *p,
struct nfsd3_readdirres *resp)
{
p = encode_post_op_attr(rqstp, p, &resp->fh);
if (resp->status == 0) {
/* stupid readdir cookie */
memcpy(p, resp->verf, 8); p += 2;
xdr_ressize_check(rqstp, p);
p = resp->buffer;
here -->> *p++ = 0; /* no more entries */
*p++ = htonl(resp->common.err == nfserr_eof);
resp->buffer is NULL because no entries were encoded. This was fixed
by Neil in 2.6.9.
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
okir@suse.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
-------------------------------------------------------
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 8:49 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 [this message]
2005-04-20 18:34 ` Steven
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=20050420084935.GA30863@suse.de \
--to=okir@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=steven@void.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