From: Chuck Lever <chuck.lever@oracle.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: steved@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] mount.nfs: set the default family for lookups based on Defaultproto= setting
Date: Fri, 05 Feb 2010 10:31:28 -0500 [thread overview]
Message-ID: <4B6C39D0.3030704@oracle.com> (raw)
In-Reply-To: <1265380055-5650-1-git-send-email-jlayton@redhat.com>
On 02/05/2010 09:27 AM, Jeff Layton wrote:
> When IPv6 is enabled, the Proto= config file option is treated as a
> netid, and the address family for lookups is selected based on that
> setting. The Defaultproto= option however still only affects the
> protocol setting for the sockets (IPPROTO_*) and not the address family.
>
> This patch makes it so that if someone sets the "Defaultproto=" option
> in the nfsmount.conf, it's used to determine the default address family
> for lookups as well as the protocol type.
>
> This gives users a way to force a particular address family to be used
> universally for mounts and brings the behavior of the Defaultproto=
> option in line with the Proto= option.
>
> Signed-off-by: Jeff Layton<jlayton@redhat.com>
> ---
> utils/mount/configfile.c | 8 ++++++++
> utils/mount/network.c | 18 ++++++++----------
> 2 files changed, 16 insertions(+), 10 deletions(-)
>
> diff --git a/utils/mount/configfile.c b/utils/mount/configfile.c
> index 6843098..71d3627 100644
> --- a/utils/mount/configfile.c
> +++ b/utils/mount/configfile.c
> @@ -221,6 +221,8 @@ int inline check_vers(char *mopt, char *field)
>
> unsigned long config_default_vers;
> unsigned long config_default_proto;
> +extern sa_family_t config_default_family;
> +
> /*
> * Check to see if a default value is being set.
> * If so, set the appropriate global value which will
> @@ -242,6 +244,12 @@ int inline default_value(char *mopt)
> xlog_warn("Unable to set default protocol : %s",
> strerror(errno));
> }
> +#ifdef IPV6_SUPPORTED
> + if (!nfs_nfs_proto_family(options,&config_default_family)) {
> + xlog_warn("Unable to set default family : %s",
> + strerror(errno));
> + }
> +#endif
Maybe you don't need the #ifdef here?
Aside from making the code more readable, removing the #ifdef would also
make it so the same code path is followed whether IPv6 is supported or
not, which makes testing easier.
Just a thought.
> } else {
> xlog_warn("Unable to alloc memory for default protocol");
> }
> diff --git a/utils/mount/network.c b/utils/mount/network.c
> index 92bba2d..0ab3bb1 100644
> --- a/utils/mount/network.c
> +++ b/utils/mount/network.c
> @@ -1331,6 +1331,12 @@ nfs_nfs_port(struct mount_options *options, unsigned long *port)
> return 1;
> }
>
> +#ifdef IPV6_SUPPORTED
> +sa_family_t config_default_family = AF_UNSPEC;
> +#else
> +sa_family_t config_default_family = AF_INET;
> +#endif
> +
> /*
> * Returns TRUE and fills in @family if a valid NFS protocol option
> * is found, or FALSE if the option was specified with an invalid value.
> @@ -1341,11 +1347,7 @@ int nfs_nfs_proto_family(struct mount_options *options,
> unsigned long protocol;
> char *option;
>
> -#ifdef IPV6_SUPPORTED
> - *family = AF_UNSPEC;
> -#else
> - *family = AF_INET;
> -#endif
> + *family = config_default_family;
>
> switch (po_rightmost(options, nfs_transport_opttbl)) {
> case 0: /* udp */
> @@ -1488,11 +1490,7 @@ int nfs_mount_proto_family(struct mount_options *options,
> unsigned long protocol;
> char *option;
>
> -#ifdef HAVE_LIBTIRPC
> - *family = AF_UNSPEC;
> -#else
> - *family = AF_INET;
> -#endif
> + *family = config_default_family;
>
> option = po_get(options, "mountproto");
> if (option != NULL)
--
chuck[dot]lever[at]oracle[dot]com
next prev parent reply other threads:[~2010-02-05 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 14:27 [PATCH] mount.nfs: set the default family for lookups based on Defaultproto= setting Jeff Layton
2010-02-05 15:31 ` Chuck Lever [this message]
2010-02-05 16:30 ` Jeff Layton
[not found] ` <20100205113052.333f0c05-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-02-05 17:13 ` Chuck Lever
2010-02-05 17:43 ` Jeff Layton
[not found] ` <20100205124340.6b77902c-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-02-05 18:11 ` Chuck Lever
2010-02-05 18:17 ` Jeff Layton
[not found] ` <20100205131757.6fd224d0-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-02-05 19:55 ` Jeff Layton
[not found] ` <20100205145530.61634593-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-02-05 19:59 ` Chuck Lever
2010-02-05 20:05 ` Jeff Layton
[not found] ` <20100205150511.5e18538f-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-02-05 20:25 ` Chuck Lever
2010-02-05 21:20 ` Jeff Layton
[not found] ` <20100205162018.41ea79d8-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-02-05 21:28 ` Chuck Lever
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=4B6C39D0.3030704@oracle.com \
--to=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox