bjschuma@xxxxxxxxx wrote: I forgot to CC the mailing list... oops. ---------- Forwarded message ---------- From: bjschuma@xxxxxxxxx <bjschuma@xxxxxxxxx> 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@xxxxxxxxxx> Cc: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>, jlayton@xxxxxxxxxx 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. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
