From: Stefan Behrens <sbehrens@giantdisaster.de>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: subvol show could take more than one subvol
Date: Fri, 19 Apr 2013 12:00:52 +0200 [thread overview]
Message-ID: <517115D4.6000105@giantdisaster.de> (raw)
In-Reply-To: <1366364309-28525-1-git-send-email-anand.jain@oracle.com>
On Fri, 19 Apr 2013 17:38:29 +0800, Anand Jain wrote:
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> cmds-subvolume.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/cmds-subvolume.c b/cmds-subvolume.c
> index 74e2130..e3b8032 100644
> --- a/cmds-subvolume.c
> +++ b/cmds-subvolume.c
> @@ -800,16 +800,18 @@ static int cmd_subvol_show(int argc, char **argv)
> struct btrfs_list_filter_set *filter_set;
> char tstr[256];
> char uuidparse[37];
> - char *fullpath = NULL, *svpath = NULL, *mnt = NULL;
> + char *fullpath, *svpath = NULL, *mnt;
> char raw_prefix[] = "\t\t\t\t";
> u64 sv_id, mntid;
> int fd = -1, mntfd = -1;
> int ret = -1;
>
> - if (check_argc_exact(argc, 2))
> + if (check_argc_min(argc, 2))
> usage(cmd_subvol_show_usage);
> -
> - fullpath = realpath(argv[1], 0);
> +again:
> + mnt = NULL;
> + fullpath = NULL;
The "fullpath = NULL" line above is not needed because of the following
line.
> + fullpath = realpath(argv[optind++], 0);
> if (!fullpath) {
> fprintf(stderr, "ERROR: finding real path for '%s', %s\n",
> argv[1], strerror(errno));
argv[optind - 1], strerror(errno));
> @@ -939,6 +941,8 @@ out:
> if (fullpath)
> free(fullpath);
>
> + if (optind < argc)
> + goto again;
> return ret;
> }
>
>
prev parent reply other threads:[~2013-04-19 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 9:38 [PATCH] btrfs-progs: subvol show could take more than one subvol Anand Jain
2013-04-19 10:00 ` Stefan Behrens [this message]
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=517115D4.6000105@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=anand.jain@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.