Return-Path: bfields@fieldses.org Date: Wed, 12 Nov 2014 15:07:02 -0500 To: Trond Myklebust Cc: Steve Dickson , Chuck Lever , Benjamin Coddington , Linux NFS Mailing List Subject: Re: mount default minor version behavior Message-ID: <20141112200702.GA8790@fieldses.org> References: <5462608B.1090607@RedHat.com> <54635BB5.1020702@RedHat.com> <5463787A.7080404@RedHat.com> <43A888DD-6114-48FC-AE99-DBE6BBF19A7B@oracle.com> <5463A282.8060803@RedHat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: From: "J. Bruce Fields" List-ID: 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. --b.