Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
To: <dsterba@suse.cz>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2 2/4] btrfs-progs: deal with invalid option combinations for btrfs-image
Date: Tue, 24 Jun 2014 10:51:54 +0800	[thread overview]
Message-ID: <1403578314.6694.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1403577393-6096-1-git-send-email-guihc.fnst@cn.fujitsu.com>

On Tue, 2014-06-24 at 10:36 +0800, Gui Hecheng wrote:
> For btrfs-image,
> 	dump 	may not come with option '-o'
> 	-r	may not come with option '-c', '-s', '-w', dev_cnt != 1
> 	-m	may not come with dev_cnt < 2
> All of the above should be regarded as invalid combinations,
> and the usage will show up.
> 
> Signed-off-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
> ---
> changelog
> 	v1->v2: add error messages for each case
> ---
>  btrfs-image.c | 24 ++++++++++++++++++------
>  1 file changed, 18 insertions(+), 6 deletions(-)
> 
> diff --git a/btrfs-image.c b/btrfs-image.c
> index db5d193..c18dff1 100644
> --- a/btrfs-image.c
> +++ b/btrfs-image.c
> @@ -2462,6 +2462,7 @@ int main(int argc, char *argv[])
>  	int ret;
>  	int sanitize = 0;
>  	int dev_cnt = 0;
> +	int usage_error = 0;
>  	FILE *out;
>  
>  	while (1) {
> @@ -2500,15 +2501,26 @@ int main(int argc, char *argv[])
>  		}
>  	}
>  
> -	if ((old_restore) && create)
> -		print_usage();
> -
>  	argc = argc - optind;
>  	dev_cnt = argc - 1;
>  
> -	if (multi_devices && dev_cnt < 2)
> -		print_usage();
> -	if (!multi_devices && dev_cnt != 1)
> +	if (create) {
> +		usage_error = old_restore;
> +		fprintf(stderr, "Usage error: create and restore cannot be used at the same time\n");
> +	} else {
> +		usage_error = walk_trees || sanitize || compress_level;
> +		fprintf(stderr, "Usage error: use -w, -s, -c options for restore makes no sense\n");
> +
> +		if (multi_devices) {
> +			usage_error = usage_error || (dev_cnt < 2);
> +			fprintf(stderr, "Usage error: not enough devices specified for -m option\n");
> +		} else {
> +			usage_error = usage_error || (dev_cnt != 1);
> +			fprintf(stderr, "Usage error: accepts only 1 device without -m option\n");
> +		}
> +	}
> +
> +	if (usage_error)
>  		print_usage();
>  
>  	source = argv[optind];
Ah, sorry, I forget about the if() judgement, please *ignore* this one.


  reply	other threads:[~2014-06-24  2:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19  1:46 [PATCH 1/4] btrfs-progs: cleanup duplicate assignment of variable leaf for btrfs-image Gui Hecheng
2014-06-19  1:46 ` [PATCH 2/4] btrfs-progs: deal with invalid option combinations " Gui Hecheng
2014-06-23 14:12   ` David Sterba
2014-06-24  1:43     ` Gui Hecheng
2014-06-24  2:36     ` [PATCH v2 " Gui Hecheng
2014-06-24  2:51       ` Gui Hecheng [this message]
2014-06-24  3:16     ` [PATCH v3 " Gui Hecheng
2014-06-19  1:46 ` [PATCH 3/4] btrfs-progs: delete invalid output file when btrfs-image failed Gui Hecheng
2014-06-23 14:15   ` David Sterba
2014-06-24  1:41     ` Gui Hecheng
2014-06-24  2:38     ` [PATCH v2 " Gui Hecheng
2014-06-24  3:05       ` Gui Hecheng
2014-06-24  3:16     ` [PATCH v3 " Gui Hecheng
2014-06-24  8:47       ` David Sterba
2014-06-19  1:46 ` [PATCH 4/4] btrfs-progs: update manpage for btrfs-image with -m option added Gui Hecheng

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=1403578314.6694.2.camel@localhost.localdomain \
    --to=guihc.fnst@cn.fujitsu.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@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