From: Eric Sandeen <sandeen@sandeen.net>
To: Xiao Yang <yangx.jy@cn.fujitsu.com>,
Christoph Hellwig <hch@infradead.org>
Cc: darrick.wong@oracle.com, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] io/attr.c: Disallow specifying both -D and -R options for chattr command
Date: Thu, 23 Jul 2020 15:15:27 -0700 [thread overview]
Message-ID: <86314935-eeb9-3c8a-5d64-7db8b36ce43d@sandeen.net> (raw)
In-Reply-To: <5F19308A.2060109@cn.fujitsu.com>
On 7/22/20 11:39 PM, Xiao Yang wrote:
> On 2020/7/23 14:08, Christoph Hellwig wrote:
>> On Thu, Jul 23, 2020 at 01:27:23PM +0800, Xiao Yang wrote:
>>> -D and -R options are mutually exclusive actually but chattr command
>>> doesn't check it so that always applies -D option when both of them
>>> are specified. For example:
>> Looks good,
>>
>> Reviewed-by: Christoph Hellwig<hch@lst.de>
> Hi,
>
> Ah, I have a question after sending the patch:
> Other commands(e.g. cowextsize) including the same options seem to avoid the issue by accepting the last option, as below:
> --------------------------------------------------------
> io/cowextsize.c
> 141 while ((c = getopt(argc, argv, "DR")) != EOF) {
> 142 switch (c) {
> 143 case 'D':
> 144 recurse_all = 0;
> 145 recurse_dir = 1;
> 146 break;
> 147 case 'R':
> 148 recurse_all = 1;
> 149 recurse_dir = 0;
> 150 break;
Yep, I meant to look at this but hadn't gotten to it yet. These should all
be consistent, and I tend to agree with Dave that explicitly conflicting
incompatible options and erroring out is better than silently accepting
the last one specified.
And indeed help specifies that they are exclusive:
cowextsize_cmd.args = _("[-D | -R] [cowextsize]");
It'd be great if you want to send a V2 that makes the behavior (and
documentation) of any/all commands that accept [-D | -R] consistent.
Thanks,
-Eric
next prev parent reply other threads:[~2020-07-23 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 5:27 [PATCH] io/attr.c: Disallow specifying both -D and -R options for chattr command Xiao Yang
2020-07-23 6:08 ` Christoph Hellwig
2020-07-23 6:39 ` Xiao Yang
2020-07-23 22:10 ` Dave Chinner
2020-07-23 22:15 ` Eric Sandeen [this message]
2020-07-24 1:09 ` Xiao Yang
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=86314935-eeb9-3c8a-5d64-7db8b36ce43d@sandeen.net \
--to=sandeen@sandeen.net \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=yangx.jy@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).