From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Steve Dickson <SteveD@redhat.com>,
Anna Schumaker <Anna.Schumaker@netapp.com>,
Chuck Lever <chuck.lever@oracle.com>,
Benjamin Coddington <bcodding@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: mount default minor version behavior
Date: Thu, 13 Nov 2014 14:02:13 -0500 [thread overview]
Message-ID: <20141113190213.GA28516@fieldses.org> (raw)
In-Reply-To: <CAHQdGtTqJDBTKZ3e9u3FgRjRbTFapEh+nYi0i+yy02Dar-ypPA@mail.gmail.com>
On Thu, Nov 13, 2014 at 01:52:09PM -0500, Trond Myklebust wrote:
> On Thu, Nov 13, 2014 at 12:57 PM, Steve Dickson <SteveD@redhat.com> wrote:
> > On 11/12/2014 05:42 PM, Trond Myklebust wrote:
> >>>> NFS v4.0, 4.1, and 4.2 are all part of the same module, though. Is there a way to analyze modules and determine what is compiled in?
> >>> > Maybe come up with some global bit field could be used?
> >>> > Each bit signifies a minor version is enabled...
> >>> >
> >> No. This means that mount.nfs now suddenly needs to know the names of
> >> the NFS modules and how to load them before it calls mount() just so
> >> that it knows which parameters to try. This is a rathole we don't want
> >> to explore...
> > I don't think mount.nfs needs to know any names... Just
> > a file /proc/fs/nfs/mount that tells mount.nfs where
> > to start the negotiation....
> >
>
> The kernel does not have that information until the NFSv4 module is loaded.
I still don't get it. All it needs to know is an upper bound--that
could be a single compile-time constant. Is there any reason not to
build that number into the main nfs module?
--b.
next prev parent reply other threads:[~2014-11-13 19:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 14:39 mount default minor version behavior Benjamin Coddington
2014-11-11 15:01 ` Weston Andros Adamson
2014-11-11 15:15 ` Benjamin Coddington
2014-11-11 15:01 ` Trond Myklebust
2014-11-11 15:20 ` Benjamin Coddington
2014-11-11 15:24 ` Trond Myklebust
2014-11-11 15:27 ` Anna Schumaker
2014-11-11 16:27 ` Boaz Harrosh
2014-11-11 19:19 ` Frank Filz
2014-11-11 19:25 ` Steve Dickson
2014-11-11 19:16 ` Steve Dickson
2014-11-11 20:43 ` Trond Myklebust
2014-11-12 13:08 ` Steve Dickson
2014-11-12 14:31 ` Trond Myklebust
2014-11-12 15:10 ` Steve Dickson
2014-11-12 15:28 ` Trond Myklebust
2014-11-12 15:37 ` Chuck Lever
2014-11-12 18:10 ` Steve Dickson
2014-11-12 18:41 ` Trond Myklebust
2014-11-12 20:07 ` J. Bruce Fields
2014-11-12 20:30 ` Steve Dickson
2014-11-12 20:17 ` Anna Schumaker
2014-11-12 20:32 ` Steve Dickson
2014-11-12 22:42 ` Trond Myklebust
2014-11-13 17:57 ` Steve Dickson
2014-11-13 18:52 ` Trond Myklebust
2014-11-13 19:02 ` J. Bruce Fields [this message]
2014-11-13 19:26 ` Trond Myklebust
2014-11-13 19:55 ` J. Bruce Fields
2014-11-13 20:22 ` Trond Myklebust
2014-11-13 20:38 ` J. Bruce Fields
2014-11-13 15:07 ` Chuck Lever
2014-11-13 20:31 ` Steve Dickson
2014-11-12 17:27 ` Steve Dickson
2014-11-11 16:38 ` Chuck Lever
2014-11-17 19:47 ` Benjamin Coddington
2014-11-17 21:02 ` Chuck Lever
2014-11-12 13:09 ` Benjamin Coddington
2014-11-12 14:36 ` Trond Myklebust
2014-11-12 15:01 ` Benjamin Coddington
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=20141113190213.GA28516@fieldses.org \
--to=bfields@fieldses.org \
--cc=Anna.Schumaker@netapp.com \
--cc=SteveD@redhat.com \
--cc=bcodding@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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.