From: suzuki <suzuki@in.ibm.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
neilb@suse.de, linux-kernel@vger.kernel.org,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
bfields@fieldses.org, nfs@lists.sourceforge.net,
ffilz@us.ibm.com, Poornima <bnpoorni@in.ibm.com>
Subject: Re: [BUG] 2.6.23-rc5 kernel BUG at fs/nfs/nfs4xdr.c:945
Date: Tue, 11 Sep 2007 10:26:10 +0530 [thread overview]
Message-ID: <46E61FEA.9010800@in.ibm.com> (raw)
In-Reply-To: <1189458228.6634.4.camel@heimdal.trondhjem.org>
Trond Myklebust wrote:
> On Mon, 2007-09-10 at 13:41 +0530, suzuki wrote:
>> Hi
>>
>> I have been trying to debug this issue from my side and could find the
>> following.
>>
>> The pathconf() request gets a reply with :
>>
>> pathinfo.max_namelen = (unsiged int) -1
>> pathinfo.max_link = 255
>>
>> Is this really an expected answer from a server for a proper connection
>> ( for mount requests on an exported dir) ? Is there something that needs
>> to be fixed at server side ?
>
> I assume that this is with my patch applied?
No. This is without your patch. So I am trying to debug why the server
is sending a -1 ! (which sounds like an error ?)
Thanks
Suzuki K P
IBM Linux Technology Centre
Yes: as long as the kernel
> sets NAME_MAX to 255, then the above is expected behaviour.
>
> Trond
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
WARNING: multiple messages have this Message-ID (diff)
From: suzuki <suzuki@in.ibm.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
bfields@fieldses.org, neilb@suse.de, nfs@lists.sourceforge.net,
linux-kernel@vger.kernel.org, ffilz@us.ibm.com,
Poornima <bnpoorni@in.ibm.com>
Subject: Re: [NFS] [BUG] 2.6.23-rc5 kernel BUG at fs/nfs/nfs4xdr.c:945
Date: Tue, 11 Sep 2007 10:26:10 +0530 [thread overview]
Message-ID: <46E61FEA.9010800@in.ibm.com> (raw)
In-Reply-To: <1189458228.6634.4.camel@heimdal.trondhjem.org>
Trond Myklebust wrote:
> On Mon, 2007-09-10 at 13:41 +0530, suzuki wrote:
>> Hi
>>
>> I have been trying to debug this issue from my side and could find the
>> following.
>>
>> The pathconf() request gets a reply with :
>>
>> pathinfo.max_namelen = (unsiged int) -1
>> pathinfo.max_link = 255
>>
>> Is this really an expected answer from a server for a proper connection
>> ( for mount requests on an exported dir) ? Is there something that needs
>> to be fixed at server side ?
>
> I assume that this is with my patch applied?
No. This is without your patch. So I am trying to debug why the server
is sending a -1 ! (which sounds like an error ?)
Thanks
Suzuki K P
IBM Linux Technology Centre
Yes: as long as the kernel
> sets NAME_MAX to 255, then the above is expected behaviour.
>
> Trond
>
next prev parent reply other threads:[~2007-09-11 4:58 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
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 [this message]
2007-09-11 4:56 ` 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=46E61FEA.9010800@in.ibm.com \
--to=suzuki@in.ibm.com \
--cc=bfields@fieldses.org \
--cc=bnpoorni@in.ibm.com \
--cc=ffilz@us.ibm.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.