public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: "Jan Ťulák" <jtulak@redhat.com>
Cc: Dave Chinner <dchinner@redhat.com>, xfs@oss.sgi.com
Subject: Re: [PATCH 05/17] mkfs: factor boolean option parsing
Date: Thu, 25 Jun 2015 15:38:40 -0400	[thread overview]
Message-ID: <20150625193840.GI36162@bfoster.bfoster> (raw)
In-Reply-To: <1434711726-13092-6-git-send-email-jtulak@redhat.com>

On Fri, Jun 19, 2015 at 01:01:54PM +0200, Jan Ťulák wrote:
> From: Dave Chinner <dchinner@redhat.com>
> 
> Many of the options passed to mkfs have boolean options (0 or 1) and
> all hand roll the same code and validity checks. Factor these out
> into a common function.
> 
> Note that the lazy-count option is now changed to match other
> booleans in that if you don't specify a value, it reverts to the
> default value (on) rather than throwing an error. Similarly the -m
> crc and -n ftype options default to off rather than throwing an
> error.
> 
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> Signed-off-by: Jan Ťulák <jtulak@redhat.com>
> ---
>  mkfs/xfs_mkfs.c | 101 +++++++++++++++++++++++---------------------------------
>  1 file changed, 42 insertions(+), 59 deletions(-)
> 
> diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> index 1a5e2f8..6b9e991 100644
> --- a/mkfs/xfs_mkfs.c
> +++ b/mkfs/xfs_mkfs.c
> @@ -42,7 +42,7 @@ struct fs_topology {
>   * Prototypes for internal functions.
>   */
>  static void conflict(char opt, char *tab[], int oldidx, int newidx);
> -static void illegal(char *value, char *opt);
> +static void illegal(const char *value, const char *opt);
>  static __attribute__((noreturn)) void usage (void);
>  static __attribute__((noreturn)) void reqval(char opt, char *tab[], int idx);
>  static void respec(char opt, char *tab[], int idx);
> @@ -1028,6 +1028,21 @@ getnum(
>  	return i;
>  }
>  
> +static bool
> +getbool(
> +	const char	*str,
> +	const char	*illegal_str,
> +	bool		default_val)
> +{
> +	long long	c;
> +
> +	if (!str || *str == '\0')
> +		return default_val;
> +	c = getnum(str, 0, 0, false);
> +	if (c < 0 || c > 1)
> +		illegal(str, illegal_str);
> +	return c ? true : false;
> +}
>  
>  int
>  main(
> @@ -1247,11 +1262,8 @@ main(
>  					dasize = 1;
>  					break;
>  				case D_FILE:
> -					if (!value || *value == '\0')
> -						value = "1";
> -					xi.disfile = getnum(value, 0, 0, false);
> -					if (xi.disfile < 0 || xi.disfile > 1)
> -						illegal(value, "d file");
> +					xi.disfile = getbool(value, "d file",
> +							     true);
>  					if (xi.disfile && !Nflag)
>  						xi.dcreat = 1;
>  					break;
> @@ -1394,12 +1406,8 @@ main(
>  
>  				switch (getsubopt(&p, (constpp)iopts, &value)) {
>  				case I_ALIGN:
> -					if (!value || *value == '\0')
> -						break;
> -					c = getnum(value, 0, 0, false);
> -					if (c < 0 || c > 1)
> -						illegal(value, "i align");
> -					sb_feat.inode_align = c ? true : false;
> +					sb_feat.inode_align = getbool(
> +							value, "i align", true);
>  					break;
>  				case I_LOG:
>  					if (!value || *value == '\0')
> @@ -1472,12 +1480,8 @@ main(
>  					sb_feat.attr_version = c;
>  					break;
>  				case I_PROJID32BIT:
> -					if (!value || *value == '\0')
> -						value = "0";
> -					c = getnum(value, 0, 0, false);
> -					if (c < 0 || c > 1)
> -						illegal(value, "i projid32bit");
> -					sb_feat.projid16bit = c ? false : true;
> +					sb_feat.projid16bit = !getbool(value,
> +							"i projid32bit", false);
>  					break;
>  				case I_SPINODES:
>  					if (!value || *value == '\0')
> @@ -1510,20 +1514,15 @@ main(
>  					laflag = 1;
>  					break;
>  				case L_FILE:
> -					if (!value || *value == '\0')
> -						value = "1";
>  					if (loginternal)
>  						conflict('l', lopts, L_INTERNAL,
>  							 L_FILE);
> -					xi.lisfile = getnum(value, 0, 0, false);
> -					if (xi.lisfile < 0 || xi.lisfile > 1)
> -						illegal(value, "l file");
> +					xi.lisfile = getbool(value, "l file",
> +							     true);
>  					if (xi.lisfile)
>  						xi.lcreat = 1;
>  					break;
>  				case L_INTERNAL:
> -					if (!value || *value == '\0')
> -						value = "1";
>  					if (ldflag)
>  						conflict('l', lopts, L_INTERNAL, L_DEV);
>  					if (xi.lisfile)
> @@ -1531,9 +1530,9 @@ main(
>  							 L_INTERNAL);
>  					if (liflag)
>  						respec('l', lopts, L_INTERNAL);
> -					loginternal = getnum(value, 0, 0, false);
> -					if (loginternal < 0 || loginternal > 1)
> -						illegal(value, "l internal");
> +
> +					loginternal = getbool(value,
> +							"l internal", true);
>  					liflag = 1;
>  					break;
>  				case L_SU:
> @@ -1623,14 +1622,9 @@ main(
>  					lssflag = 1;
>  					break;
>  				case L_LAZYSBCNTR:
> -					if (!value || *value == '\0')
> -						reqval('l', lopts,
> -								L_LAZYSBCNTR);
> -					c = getnum(value, 0, 0, false);
> -					if (c < 0 || c > 1)
> -						illegal(value, "l lazy-count");
> -					sb_feat.lazy_sb_counters = c ? true
> -								     : false;
> +					sb_feat.lazy_sb_counters = getbool(
> +							value, "l lazy-count",
> +							true);
>  					break;
>  				default:
>  					unknown('l', value);
> @@ -1649,18 +1643,14 @@ main(
>  
>  				switch (getsubopt(&p, (constpp)mopts, &value)) {
>  				case M_CRC:
> -					if (!value || *value == '\0')
> -						reqval('m', mopts, M_CRC);
> -					c = getnum(value, 0, 0, false);
> -					if (c < 0 || c > 1)
> -						illegal(value, "m crc");
> -					if (c && nftype) {
> +					sb_feat.crcs_enabled = getbool(
> +							value, "m crc", false);

Hmm... so I know we have crc on by default now, but it seems a little
weird to me for '-m crc' to turn it off.

> +					if (sb_feat.crcs_enabled && nftype) {
>  						fprintf(stderr,
> -_("cannot specify both crc and ftype\n"));
> +_("cannot specify both -m crc=1 and -n ftype\n"));
>  						usage();
>  					}
> -					sb_feat.crcs_enabled = c ? true : false;
> -					if (c)
> +					if (sb_feat.crcs_enabled)
>  						sb_feat.dirftype = true;
>  					break;
>  				case M_FINOBT:

No getbool() update for finobt?

> @@ -1731,19 +1721,15 @@ _("cannot specify both crc and ftype\n"));
>  					nvflag = 1;
>  					break;
>  				case N_FTYPE:
> -					if (!value || *value == '\0')
> -						reqval('n', nopts, N_FTYPE);
>  					if (nftype)
>  						respec('n', nopts, N_FTYPE);
> -					c = getnum(value, 0, 0, false);
> -					if (c < 0 || c > 1)
> -						illegal(value, "n ftype");
>  					if (sb_feat.crcs_enabled) {
>  						fprintf(stderr,
> -_("cannot specify both crc and ftype\n"));
> +_("cannot specify both -m crc=1 and -n ftype\n"));
>  						usage();
>  					}
> -					sb_feat.dirftype = c ? true : false;
> +					sb_feat.dirftype = getbool(value,
> +							     "n ftype", false);

Similar weirdness here, IMO. Using '-m crc -n ftype' gives an fs without
either. The toggling behavior is consistent I suppose, but it seems
really nonintuitive to me. I would expect the act of specifying
something as an implicit request to enable, regardless of the
application specific defaults (that do change once in a while).

Brian

>  					nftype = 1;
>  					break;
>  				default:
> @@ -1779,11 +1765,8 @@ _("cannot specify both crc and ftype\n"));
>  					rtextsize = value;
>  					break;
>  				case R_FILE:
> -					if (!value || *value == '\0')
> -						value = "1";
> -					xi.risfile = getnum(value, 0, 0, false);
> -					if (xi.risfile < 0 || xi.risfile > 1)
> -						illegal(value, "r file");
> +					xi.risfile = getbool(value,
> +							     "r file", true);
>  					if (xi.risfile)
>  						xi.rcreat = 1;
>  					break;
> @@ -3228,8 +3211,8 @@ conflict(
>  
>  static void
>  illegal(
> -	char		*value,
> -	char		*opt)
> +	const char	*value,
> +	const char	*opt)
>  {
>  	fprintf(stderr, _("Illegal value %s for -%s option\n"), value, opt);
>  	usage();
> -- 
> 2.1.0
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-06-25 19:38 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 11:01 [PATCH 00/17] mkfs: sanitise input parameters Jan Ťulák
2015-06-19 11:01 ` [PATCH 01/17] xfsprogs: use common code for multi-disk detection Jan Ťulák
2015-06-19 11:10   ` Christoph Hellwig
2015-06-19 11:51     ` Jan Tulak
2015-06-25 19:37   ` Brian Foster
2015-07-02 12:47     ` Jan Tulak
2015-07-02 14:14       ` Brian Foster
2015-07-02 23:05         ` Dave Chinner
2015-07-03 13:22           ` Brian Foster
2015-07-08 16:14           ` Jan Tulak
2015-07-09  0:45             ` Dave Chinner
2015-07-09  8:24               ` Jan Tulak
2015-07-03 10:06         ` Jan Tulak
2015-06-19 11:01 ` [PATCH 02/17] mkfs: sanitise ftype parameter values Jan Ťulák
2015-06-25 19:37   ` Brian Foster
2015-06-19 11:01 ` [PATCH 03/17] mkfs: Sanitise the superblock feature macros Jan Ťulák
2015-06-25 19:38   ` Brian Foster
2015-07-03  9:53     ` Jan Tulak
2015-07-03 13:24       ` Brian Foster
2015-06-19 11:01 ` [PATCH 04/17] mkfs: validate all input values Jan Ťulák
2015-06-25 19:38   ` Brian Foster
2015-06-19 11:01 ` [PATCH 05/17] mkfs: factor boolean option parsing Jan Ťulák
2015-06-25 19:38   ` Brian Foster [this message]
2015-06-19 11:01 ` [PATCH 06/17] mkfs: validate logarithmic parameters sanely Jan Ťulák
2015-06-26 17:16   ` Brian Foster
2015-06-19 11:01 ` [PATCH 07/17] mkfs: structify input parameter passing Jan Ťulák
2015-06-26 17:16   ` Brian Foster
2015-06-19 11:01 ` [PATCH 08/17] mkfs: getbool is redundant Jan Ťulák
2015-06-26 17:17   ` Brian Foster
2015-06-30  1:32     ` Dave Chinner
2015-06-19 11:01 ` [PATCH 09/17] mkfs: use getnum_checked for all ranged parameters Jan Ťulák
2015-06-26 17:17   ` Brian Foster
2015-06-19 11:01 ` [PATCH 10/17] mkfs: add respecification detection to generic parsing Jan Ťulák
2015-06-26 17:17   ` Brian Foster
2015-06-19 11:02 ` [PATCH 11/17] mkfs: table based parsing for converted parameters Jan Ťulák
2015-06-26 17:17   ` Brian Foster
2015-06-19 11:02 ` [PATCH 12/17] mkfs: merge getnum Jan Ťulák
2015-06-26 17:17   ` Brian Foster
2015-06-19 11:02 ` [PATCH 13/17] mkfs: encode conflicts into parsing table Jan Ťulák
2015-06-26 17:17   ` Brian Foster
2015-06-30  3:57     ` Dave Chinner
2015-06-30 11:27       ` Brian Foster
2015-07-01  8:30         ` Jan Tulak
2015-06-19 11:02 ` [PATCH 14/17] mkfs: add string options to generic parsing Jan Ťulák
2015-06-26 19:32   ` Brian Foster
2015-06-19 11:02 ` [PATCH 15/17] mkfs: don't treat files as though they are block devices Jan Ťulák
2015-06-26 19:32   ` Brian Foster
2015-06-19 11:02 ` [PATCH 16/17] mkfs fix: handling of files Jan Ťulák
2015-06-26 19:32   ` Brian Foster
2015-06-19 11:02 ` [PATCH 17/17] mkfs: move spinodes crc check Jan Ťulák
2015-06-26 19:32   ` Brian Foster

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=20150625193840.GI36162@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=dchinner@redhat.com \
    --cc=jtulak@redhat.com \
    --cc=xfs@oss.sgi.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