From: Jeff Layton <jlayton@redhat.com>
To: Josh Boyer <jwboyer@redhat.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NFSv4: Add modalias for "nfs4"
Date: Fri, 27 Apr 2012 09:30:47 -0400 [thread overview]
Message-ID: <20120427093047.121bd01b@corrin.poochiereds.net> (raw)
In-Reply-To: <20120427131031.GA13189@zod.bos.redhat.com>
On Fri, 27 Apr 2012 09:10:33 -0400
Josh Boyer <jwboyer@redhat.com> wrote:
> When NFSv4 is configured, the support goes into the nfs.ko module.
> However, nfs-utils seems to pass "nfs4" as the fileststem type for
> NFSv4 mounts. If the nfs module is not already loaded, the kernel
> will eventually do a module request for "nfs4". Apparently, this
> has worked until now as the distributions ship a module config file
> that manually aliases "nfs4" to "nfs".
>
> There is really no need to do this, as the kernel can provide a
> module alias internally for nfs4. This adds that.
>
> Signed-off-by: Josh Boyer <jwboyer@redhat.com>
> ---
> fs/nfs/nfs4proc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
> index 60d5f4c..d6929c3 100644
> --- a/fs/nfs/nfs4proc.c
> +++ b/fs/nfs/nfs4proc.c
> @@ -6550,6 +6550,7 @@ const struct xattr_handler *nfs4_xattr_handlers[] = {
> module_param(max_session_slots, ushort, 0644);
> MODULE_PARM_DESC(max_session_slots, "Maximum number of outstanding NFSv4.1 "
> "requests the client will negotiate");
> +MODULE_ALIAS("nfs4");
>
> /*
> * Local variables:
Looks reasonable to me.
Reviewed-by: Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2012-04-27 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 13:10 [PATCH] NFSv4: Add modalias for "nfs4" Josh Boyer
2012-04-27 13:30 ` Jeff Layton [this message]
2012-04-27 14:19 ` Jim Rees
2012-04-27 14:48 ` Josh Boyer
2012-04-27 14:50 ` Myklebust, Trond
2012-04-27 14:53 ` Josh Boyer
2012-04-27 15:02 ` Myklebust, Trond
2012-04-27 15:14 ` Josh Boyer
2012-04-27 15:21 ` Myklebust, Trond
2012-04-27 15:41 ` Josh Boyer
2012-04-27 15:27 ` Jeff Layton
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=20120427093047.121bd01b@corrin.poochiereds.net \
--to=jlayton@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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