From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: neilb@suse.de, Trond Myklebust <trond@netapp.com>,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.23-rc5 kernel BUG at fs/nfs/nfs4xdr.c:945
Date: Fri, 7 Sep 2007 11:29:13 -0400 [thread overview]
Message-ID: <20070907152913.GF24638@fieldses.org> (raw)
In-Reply-To: <46E121B8.4080105@linux.vnet.ibm.com>
On Fri, Sep 07, 2007 at 03:32:32PM +0530, Kamalesh Babulal wrote:
> Sep 7 11:42:49 p55lp2 kernel: kernel BUG at fs/nfs/nfs4xdr.c:945!
That's the first line of encode_lookup:
static int encode_lookup(struct xdr_stream *xdr, const struct qstr *name)
{
int len = name->len;
__be32 *p;
RESERVE_SPACE(8 + len);
So len is either very large, or it's just garbage. Do you know if
fsstress is trying to do something with a particularly long filename
here?
--b.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
WARNING: multiple messages have this Message-ID (diff)
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, neilb@suse.de,
nfs@lists.sourceforge.net, Trond Myklebust <trond@netapp.com>
Subject: Re: [BUG] 2.6.23-rc5 kernel BUG at fs/nfs/nfs4xdr.c:945
Date: Fri, 7 Sep 2007 11:29:13 -0400 [thread overview]
Message-ID: <20070907152913.GF24638@fieldses.org> (raw)
In-Reply-To: <46E121B8.4080105@linux.vnet.ibm.com>
On Fri, Sep 07, 2007 at 03:32:32PM +0530, Kamalesh Babulal wrote:
> Sep 7 11:42:49 p55lp2 kernel: kernel BUG at fs/nfs/nfs4xdr.c:945!
That's the first line of encode_lookup:
static int encode_lookup(struct xdr_stream *xdr, const struct qstr *name)
{
int len = name->len;
__be32 *p;
RESERVE_SPACE(8 + len);
So len is either very large, or it's just garbage. Do you know if
fsstress is trying to do something with a particularly long filename
here?
--b.
next prev parent reply other threads:[~2007-09-07 15:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 10:02 [BUG] 2.6.23-rc5 kernel BUG at fs/nfs/nfs4xdr.c:945 Kamalesh Babulal
2007-09-07 15:29 ` J. Bruce Fields [this message]
2007-09-07 15:29 ` J. Bruce Fields
2007-09-10 18:02 ` Kamalesh Babulal
2007-09-07 23:56 ` Michal Piotrowski
2007-09-07 23:56 ` Michal Piotrowski
2007-09-08 22:12 ` Trond Myklebust
2007-09-08 22:12 ` [NFS] " Trond Myklebust
2007-09-10 8:11 ` suzuki
2007-09-10 8:11 ` [NFS] " suzuki
2007-09-10 21:03 ` Trond Myklebust
2007-09-11 4:56 ` suzuki
2007-09-11 4:56 ` [NFS] " suzuki
2007-09-10 13:06 ` Kamalesh Babulal
2007-09-19 17:31 ` Trond Myklebust
2007-09-19 17:31 ` [NFS] " Trond Myklebust
2007-09-24 19:01 ` Kamalesh Babulal
2007-09-24 21:26 ` Trond Myklebust
2007-09-24 21:26 ` [NFS] " Trond Myklebust
2007-09-28 12:05 ` Kamalesh Babulal
2007-09-10 12:56 ` Kamalesh Babulal
2007-09-10 12:56 ` Kamalesh Babulal
-- strict thread matches above, loose matches on Subject: below --
2007-09-07 7:46 Kamalesh Babulal
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=20070907152913.GF24638@fieldses.org \
--to=bfields@fieldses.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=trond@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.