From: Steve Dickson <SteveD@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>,
Trond Myklebust <trond.myklebust@primarydata.com>
Cc: 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: Wed, 12 Nov 2014 15:30:20 -0500 [thread overview]
Message-ID: <5463C35C.50804@RedHat.com> (raw)
In-Reply-To: <20141112200702.GA8790@fieldses.org>
On 11/12/2014 03:07 PM, J. Bruce Fields wrote:
> On Wed, Nov 12, 2014 at 01:41:03PM -0500, Trond Myklebust wrote:
>> The NFS client modules are loaded on demand. The kernel will therefore
>> not actually know the capabilities until we attempt the mount.
>
> Right, but the main nfs module can know at least an upper bound, and
> that's all mount needs to start negotiation, isn't it? If the kernel
> thinks 4.99 is supported but in fact that module turns out to be
> blacklisted or something, then we can always try it and fall back.
>
Right, all mount.nfs needs to know is where to start...
I was thinking mount.nfs to try to load the module but
that's probably not a good idea...
steved.
next prev parent reply other threads:[~2014-11-12 20:30 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 [this message]
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
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=5463C35C.50804@RedHat.com \
--to=steved@redhat.com \
--cc=bcodding@redhat.com \
--cc=bfields@fieldses.org \
--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.