From: Eric Sandeen <sandeen@redhat.com>
To: Wang Shilong <wangshilong1991@gmail.com>
Cc: "linux-btrfs@vger.kernel.org Btrfs" <linux-btrfs@vger.kernel.org>,
"dsterba@suse.cz Sterba" <dsterba@suse.cz>,
Miao Xie <miaox@cn.fujitsu.com>,
Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Subject: Re: [PATCH] btrfs-progs: tidy up cmd_subvol_create() whitespace & returns
Date: Tue, 03 Sep 2013 10:50:15 -0500 [thread overview]
Message-ID: <52260537.6090103@redhat.com> (raw)
In-Reply-To: <0A5B4F8C-8B08-4976-A660-6396407E932D@gmail.com>
On 9/3/13 8:13 AM, Wang Shilong wrote:
> Hello Eric,
>
> Recently, i notice btrfs-progs's magic return value. For example, EACCESS return 12.
> Magic return value is confusing for code reviewers. However,at least we should guarantee
> all these conditions return the same value(for example 12 for this case)
>
> Or we can change all the magic number to 1. Miao reminded me that
> there may be some applications that have catched and checked these
> magic return values…
>
> Any ideas about this?
I think that if we want to do anything different from the standard, expected
"return 1 and set errno" then it needs to be a careful design decision, documented,
used consistently, and tested.
As far as I can tell, what is in btrfs-progs today is undocumented,
untested, and only occasionally/randomly used. Therefore I don't
think it's useful as it stands today, and why I had started removing
them.
-Eric
> Thanks,
> Wang
>> From:
>> Just whitespace fixes, and magical return value removal.
>>
>> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>> ---
>> cmds-subvolume.c | 18 +++++++++---------
>> 1 file changed, 9 insertions(+), 9 deletions(-)
>>
>> diff --git a/cmds-subvolume.c b/cmds-subvolume.c
>> index 01b982c..a9999ac 100644
>> --- a/cmds-subvolume.c
>> +++ b/cmds-subvolume.c
>> @@ -104,9 +104,9 @@ static int cmd_subvol_create(int argc, char **argv)
>> dst = argv[optind];
>>
>> res = test_isdir(dst);
>> - if(res >= 0 ){
>> + if (res >= 0) {
>> fprintf(stderr, "ERROR: '%s' exists\n", dst);
>> - return 12;
>> + return 1;
>> }
>>
>> newname = strdup(dst);
>> @@ -114,24 +114,24 @@ static int cmd_subvol_create(int argc, char **argv)
>> dstdir = strdup(dst);
>> dstdir = dirname(dstdir);
>>
>> - if( !strcmp(newname,".") || !strcmp(newname,"..") ||
>> + if (!strcmp(newname, ".") || !strcmp(newname, "..") ||
>> strchr(newname, '/') ){
>> fprintf(stderr, "ERROR: uncorrect subvolume name ('%s')\n",
>> newname);
>> - return 14;
>> + return 1;
>> }
>>
>> len = strlen(newname);
>> if (len == 0 || len >= BTRFS_VOL_NAME_MAX) {
>> fprintf(stderr, "ERROR: subvolume name too long ('%s)\n",
>> newname);
>> - return 14;
>> + return 1;
>> }
>>
>> fddst = open_file_or_dir(dstdir);
>> if (fddst < 0) {
>> fprintf(stderr, "ERROR: can't access to '%s'\n", dstdir);
>> - return 12;
>> + return 1;
>> }
>>
>> printf("Create subvolume '%s/%s'\n", dstdir, newname);
>> @@ -159,10 +159,10 @@ static int cmd_subvol_create(int argc, char **argv)
>> close(fddst);
>> free(inherit);
>>
>> - if(res < 0 ){
>> - fprintf( stderr, "ERROR: cannot create subvolume - %s\n",
>> + if (res < 0) {
>> + fprintf(stderr, "ERROR: cannot create subvolume - %s\n",
>> strerror(e));
>> - return 11;
>> + return 1;
>> }
>>
>> return 0;
>> --
>> 1.7.11.7
>>
>
next prev parent reply other threads:[~2013-09-03 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1378213291-1034-1-git-send-email-wangshilong1991@gmail.com>
2013-09-03 13:13 ` [PATCH] btrfs-progs: tidy up cmd_subvol_create() whitespace & returns Wang Shilong
2013-09-03 15:50 ` Eric Sandeen [this message]
2013-09-04 1:20 ` Wang Shilong
2013-09-04 1:24 ` Eric Sandeen
2013-09-04 1:40 ` Wang Shilong
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=52260537.6090103@redhat.com \
--to=sandeen@redhat.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=wangshilong1991@gmail.com \
--cc=wangsl.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).