From: Jim Rees <rees@umich.edu>
To: "bjschuma@gmail.com" <bjschuma@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/2] NFS: Fix a regression when loading the NFS v4 module
Date: Wed, 8 Aug 2012 15:40:21 -0400 [thread overview]
Message-ID: <20120808194021.GA24950@umich.edu> (raw)
In-Reply-To: <CAMFXNOw0G4Yp0GZmetF6akD=YqKyXBL9aoFq=kF2wiEPwPhU0w@mail.gmail.com>
bjschuma@gmail.com wrote:
I forgot to CC the mailing list... oops.
---------- Forwarded message ----------
From: bjschuma@gmail.com <bjschuma@gmail.com>
Date: Wed, Aug 8, 2012 at 1:57 PM
Subject: [PATCH 1/2] NFS: Fix a regression when loading the NFS v4 module
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, jlayton@redhat.com
Some systems have a modprobe.d/nfs.conf file that sets an nfs4 alias
pointing to nfs.ko, rather than nfs4.ko. This can prevent the v4 module
from loading on mount, since the kernel sees that something named "nfs4"
has already been loaded. To work around this, I've renamed the modules
to "nfsv2.ko" "nfsv3.ko" and "nfsv4.ko".
Is there no better way to do this? We tried for years to standardize on
nfs4 rather than nfsv4. In particular, this means the module name will no
longer be part of the names of the files used to build the module.
prev parent reply other threads:[~2012-08-08 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMFXNOztZkvP963ZWAa72aAj3ydJvhLgxU2m8_20bsZV3uqwLQ@mail.gmail.com>
2012-08-08 18:01 ` [PATCH 1/2] NFS: Fix a regression when loading the NFS v4 module bjschuma
2012-08-08 19:40 ` Jim Rees [this message]
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=20120808194021.GA24950@umich.edu \
--to=rees@umich.edu \
--cc=bjschuma@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/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).