From: "J. Bruce Fields" <bfields@fieldses.org>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: linux-nfs@vger.kernel.org, steved@redhat.com
Subject: Re: nfs-utils-1.2.9 does not play well with linux 3.10.x
Date: Mon, 16 Dec 2013 15:23:45 -0500 [thread overview]
Message-ID: <20131216202345.GF31816@fieldses.org> (raw)
In-Reply-To: <OF149AE409.624B2B0A-ONC1257C43.006F77D7-C1257C43.006FCED2@transmode.se>
On Mon, Dec 16, 2013 at 09:21:15PM +0100, Joakim Tjernlund wrote:
> "J. Bruce Fields" <bfields@fieldses.org> wrote on 2013/12/16 21:03:01:
>
> > From: "J. Bruce Fields" <bfields@fieldses.org>
> > To: Joakim Tjernlund <joakim.tjernlund@transmode.se>,
> > Cc: linux-nfs@vger.kernel.org, steved@redhat.com
> > Date: 2013/12/16 21:03
> > Subject: Re: nfs-utils-1.2.9 does not play well with linux 3.10.x
> >
> > On Mon, Dec 16, 2013 at 01:54:19PM -0500, bfields wrote:
> > > On Mon, Dec 16, 2013 at 07:16:00PM +0100, Joakim Tjernlund wrote:
> > > > rpc.nfsd insists on adding "-4.2" when writing
> /proc/fs/nfsd/versions :
> > > > rpc.nfsd: Writing version string to kernel: +4.1 -4.2 -2 +3 +4
> > > > Which causes Linux to return an EIVAL error as 3.10 has no support
> for 4.2
> > > > and
> > > > does not accept any reference to 4.2
> > > >
> > > > It seems reasonable to me that Linux should accpect -4.2 as a noop
> and
> > > > continue
> > > > processing the rest of the options but I am just guessing.
> > > > Anyhow, just to test I applied this commit to my 3.10.24 kernel:
> > > >
> > > >
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4bdc33ed5bd9fbaa243bda6fdccb22674aed6305
>
> > > > and now it accepts the "-4.2" but I have no idea if this messes up
> > > > something else.
> > >
> > > That should be perfectly safe.
>
> Thanks, I will keep this then until nfs-utils is working.
>
> > >
> > > I agree that we should teach the kernel to treat "-4.x" at least as a
> > > no-op for unknown .x. But nfs-utils also has to keep working with
> older
> > > kernels which don't do that.
> > >
> > > The problem was introduced by 12a590f8d556c00a9502eeebaa763d906222d521
> > > "rpc.nfsd: Allow v4.2 server support with the -V option". That should
> > > be using an array of ints not a bit array, so it can make the
> > > distinction between "off", "on", and "don't care".
> >
> > So, something like this (untested).--b.
>
> I tested this on my system(which has the above kernel patch) and I noticed
> a difference:
Thanks!
> rpc.nfsd: Writing version string to kernel: -2 +3 +4
> which is different than previous
> rpc.nfsd: Writing version string to kernel: +4.1 -4.2 -2 +3 +4
>
> The "+4.1" is missing.
Yes, that's intentional. Is it causing you any problem?
--b.
next prev parent reply other threads:[~2013-12-16 20:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 18:16 nfs-utils-1.2.9 does not play well with linux 3.10.x Joakim Tjernlund
2013-12-16 18:54 ` J. Bruce Fields
2013-12-16 20:03 ` J. Bruce Fields
2013-12-16 20:21 ` Joakim Tjernlund
2013-12-16 20:23 ` J. Bruce Fields [this message]
2013-12-16 22:24 ` Joakim Tjernlund
2013-12-17 3:38 ` J. Bruce Fields
2013-12-17 6:30 ` Joakim Tjernlund
2013-12-17 15:24 ` J. Bruce Fields
2013-12-17 3:43 ` [PATCH] nfsd: fix minorversion-choosing interface J. Bruce Fields
2014-01-07 21:02 ` Steve Dickson
2014-01-07 22:23 ` Joakim Tjernlund
2014-01-09 16:06 ` Steve Dickson
2014-01-09 16:26 ` Joakim Tjernlund
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=20131216202345.GF31816@fieldses.org \
--to=bfields@fieldses.org \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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 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).