From: Chuck Lever <chuck.lever@oracle.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] Fixed compile errors when the mount config file is not enabled
Date: Tue, 27 Oct 2009 16:20:47 -0400 [thread overview]
Message-ID: <36FDE8D9-4D83-447F-A2AF-516B5FEFDAD7@oracle.com> (raw)
In-Reply-To: <4AE751CE.1050300-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
Hi-
On Oct 27, 2009, at 4:02 PM, Steve Dickson wrote:
> Author: Steve Dickson <steved@redhat.com>
> Date: Tue Oct 27 15:47:27 2009 -0400
>
> Added wrappers around the setting of default values
> from the config file which will be compiled out
> when the config file is not enabled.
>
> Signed-off-by: Steve Dickson <steved@redhat.com>
>
> diff --git a/support/include/conffile.h b/support/include/conffile.h
> index fe23ec2..ce7aa21 100644
> --- a/support/include/conffile.h
> +++ b/support/include/conffile.h
> @@ -76,10 +76,5 @@ static inline void upper2lower(char *str)
> *str++ = c;
> }
>
> -/*
> - * Default Mount options
> - */
> -extern unsigned long config_default_vers;
> -extern unsigned long config_default_proto;
>
> #endif /* _CONFFILE_H_ */
> diff --git a/utils/mount/network.c b/utils/mount/network.c
> index e651167..d4ecbc9 100644
> --- a/utils/mount/network.c
> +++ b/utils/mount/network.c
> @@ -172,6 +172,27 @@ static const unsigned long probe_mnt3_first[] = {
> 0,
> };
>
> +inline const unsigned int *set_default_proto(void);
The "inline" directives are visual clutter, really... shouldn't this
be "static" instead (which in most normal cases implies "inline")?
Otherwise, you also clutter up the linker's symbol name space with
these generic function names. I've been prefixing function names with
"nfs_" for most global functions, to make debugging easier.
Why is a forward declaration needed for this function?
> +#ifdef MOUNT_CONFIG
> +inline const unsigned int *set_default_proto()
> +{
> + extern unsigned long config_default_proto;
> + /*
> + * If the default proto has been set and
> + * its not TCP, start with UDP
> + */
> + if (config_default_proto && config_default_proto != IPPROTO_TCP)
> + return probe_udp_first;
> +
> + return probe_tcp_first;
> +}
> +#else
> +inline const unsigned int *set_default_proto()
> +{
> + return probe_tcp_first;
> +}
> +#endif /* MOUNT_CONFIG */
> +
> static int nfs_lookup(const char *hostname, const sa_family_t family,
> struct sockaddr *sap, socklen_t *salen)
> {
> @@ -590,7 +611,6 @@ out_ok:
> nfs_clear_rpc_createerr();
> return 1;
> }
> -
> /*
> * Probe a server's NFS service to determine which versions and
> * transport protocols are supported.
> @@ -611,14 +631,9 @@ static int nfs_probe_nfsport(const struct
> sockaddr *sap, const socklen_t salen,
> return 1;
>
> if (nfs_mount_data_version >= 4) {
> - const unsigned int *probe_proto = probe_tcp_first;
> + const unsigned int *probe_proto;
>
> - /*
> - * If the default proto has been set and
> - * its not TCP, start with UDP
> - */
> - if (config_default_proto && config_default_proto != IPPROTO_TCP)
> - probe_proto = probe_udp_first;
> + probe_proto = set_default_proto();
>
> return nfs_probe_port(sap, salen, pmap,
> probe_nfs3_first, probe_proto);
> diff --git a/utils/mount/stropts.c b/utils/mount/stropts.c
> index ceefdb0..7b63b45 100644
> --- a/utils/mount/stropts.c
> +++ b/utils/mount/stropts.c
> @@ -93,6 +93,24 @@ struct nfsmount_info {
> child; /* forked bg child? */
> };
>
> +inline void set_default_version(struct nfsmount_info *mi);
> +#ifdef MOUNT_CONFIG
> +inline void set_default_version(struct nfsmount_info *mi)
> +{
> + extern unsigned long config_default_vers;
> + /*
> + * Use the default value set in the config file when
> + * the version has not been explicitly set.
> + */
> + if (mi->version == 0 && config_default_vers) {
> + if (config_default_vers < 4)
> + mi->version = config_default_vers;
> + }
> +}
> +#else
> +inline void set_default_version(struct nfsmount_info *mi) {}
> +#endif /* MOUNT_CONFIG */
Er. See recent patch I posted that created a nfs_set_version()
function, that is useful for a variety of purposes. Could we build on
that instead?
> +
> /*
> * Obtain a retry timeout value based on the value of the "retry="
> option.
> *
> @@ -258,7 +276,6 @@ static int nfs_append_sloppy_option(struct
> mount_options *options)
> return 0;
> return 1;
> }
> -
Whitespace nit: other function declarations in this source file are
separated by a single blank line.
> /*
> * Set up mandatory non-version specific NFS mount options.
> *
> @@ -284,14 +301,12 @@ static int nfs_validate_options(struct
> nfsmount_info *mi)
> if (option && strcmp(option, "rdma") == 0)
> mi->version = 3;
> }
> +
> /*
> - * Use the default value set in the config file when
> - * the version has not been explicitly set.
> + * If enabled, see if the default version was
> + * set in the config file
> */
> - if (mi->version == 0 && config_default_vers) {
> - if (config_default_vers < 4)
> - mi->version = config_default_vers;
> - }
> + set_default_version(mi);
>
> if (!nfs_append_sloppy_option(mi->options))
> return 0;
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
next prev parent reply other threads:[~2009-10-27 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 20:02 [PATCH] Fixed compile errors when the mount config file is not enabled Steve Dickson
[not found] ` <4AE751CE.1050300-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-10-27 20:20 ` Chuck Lever [this message]
2009-11-03 15:23 ` Steve Dickson
2009-11-16 18:28 ` Steve Dickson
2009-10-28 12:20 ` Peter Staubach
2009-11-03 14:54 ` Steve Dickson
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=36FDE8D9-4D83-447F-A2AF-516B5FEFDAD7@oracle.com \
--to=chuck.lever@oracle.com \
--cc=SteveD@redhat.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