From: "'J. Bruce Fields'" <bfields@fieldses.org>
To: Txema Heredia <txema.heredia@upf.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFSv4 memory allocation bug?
Date: Tue, 8 Feb 2011 19:09:21 -0500 [thread overview]
Message-ID: <20110209000921.GA13617@fieldses.org> (raw)
In-Reply-To: <B5CA5C80A1BA4CFAA7CBB56F752F6337@ws075402>
On Tue, Feb 08, 2011 at 07:07:08PM +0100, Txema Heredia wrote:
> Hi all,
>
> After a month or so struggling with this, and some other problems with NFSD
> in my "old" kernel (2.6.16.60-0.39.3-smp) related with MTUs larger than 1500
> stalling the server, I think I have found something related with my
> inability to serve v4 filesystems:
>
> In /usr/src/linux/include/linux/nfsd/const.h there is this defined:
> /*
> * Maximum protocol version supported by knfsd
> */
> #define NFSSVC_MAXVERS 3
>
> And in /usr/src/linux/fs/nfsd/nfsctl.c we can find this:
> err = -EINVAL;
> if (data->gd_version < 2 || data->gd_version > NFSSVC_MAXVERS)
> goto out;
> ...
> out:
> return err;
>
>
> And I found exactly the same in 2.6.34.7
>
> Is this "real" or some old thing that is no longer used and I shouldn't
> worry about?
Probably irrelevant.
Could you tell us exactly what you've tried to do and why it's failing?
--b.
next prev parent reply other threads:[~2011-02-09 0:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 17:14 NFSv4 memory allocation bug? Txema Heredia Genestar
2011-01-12 18:35 ` J. Bruce Fields
2011-01-13 15:48 ` Txema Heredia Genestar
2011-01-13 16:19 ` J. Bruce Fields
2011-01-13 17:25 ` Txema Heredia Genestar
2011-01-13 18:05 ` J. Bruce Fields
2011-01-14 12:11 ` Txema Heredia Genestar
2011-02-08 18:07 ` Txema Heredia
2011-02-09 0:09 ` 'J. Bruce Fields' [this message]
2011-02-09 13:57 ` Txema Heredia Genestar
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=20110209000921.GA13617@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=txema.heredia@upf.edu \
/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).