From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: sandeen@sandeen.net, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs_io: clean up the funshare command a bit
Date: Tue, 6 Jul 2021 11:28:56 -0700 [thread overview]
Message-ID: <20210706182856.GC11588@locust> (raw)
In-Reply-To: <YOMjJmxA7WjO8kGq@infradead.org>
On Mon, Jul 05, 2021 at 04:20:06PM +0100, Christoph Hellwig wrote:
> On Fri, Jul 02, 2021 at 07:58:08PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > Add proper argument parsing to the funshare command so that when you
> > pass it nonexistent --help it will print the help instead of complaining
> > that it can't convert that to a number.
> >
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > ---
> > io/prealloc.c | 16 ++++++++++++----
> > 1 file changed, 12 insertions(+), 4 deletions(-)
> >
> >
> > diff --git a/io/prealloc.c b/io/prealloc.c
> > index 2ae8afe9..94cf326f 100644
> > --- a/io/prealloc.c
> > +++ b/io/prealloc.c
> > @@ -346,16 +346,24 @@ funshare_f(
> > char **argv)
> > {
> > xfs_flock64_t segment;
> > + int c;
> > int mode = FALLOC_FL_UNSHARE_RANGE;
> > - int index = 1;
> >
> > - if (!offset_length(argv[index], argv[index + 1], &segment)) {
> > + while ((c = getopt(argc, argv, "")) != EOF) {
> > + switch (c) {
> > + default:
> > + command_usage(&funshare_cmd);
> > + }
>
> Do we really need this switch boilerplate?
Sort of -- without it, you get interactions like:
$ xfs_io -c 'funshare 0 --help' /autoexec.bat
non-numeric length-argument -- --help
which is silly, since we could display the help screen.
The other solution might be to fix all the offset_length() callers to
emit command usage when the number parsing doesn't work, but that would
clutter up the error reporting when you try to feed it a number that
doesn't parse.
> > + }
> > + if (optind != argc - 2)
> > + return command_usage(&funshare_cmd);
>
> Spaces instead of tabs here.
Fixed.
--D
next prev parent reply other threads:[~2021-07-06 18:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 2:57 [PATCHSET 0/2] xfs_io: small fixes to funshare command Darrick J. Wong
2021-07-03 2:58 ` [PATCH 1/2] xfs_io: fix broken funshare_cmd usage Darrick J. Wong
2021-07-05 15:16 ` Christoph Hellwig
2021-07-06 18:24 ` Darrick J. Wong
2021-07-08 7:23 ` Carlos Maiolino
2021-07-03 2:58 ` [PATCH 2/2] xfs_io: clean up the funshare command a bit Darrick J. Wong
2021-07-05 15:20 ` Christoph Hellwig
2021-07-06 18:28 ` Darrick J. Wong [this message]
2021-07-08 7:31 ` Carlos Maiolino
-- strict thread matches above, loose matches on Subject: below --
2021-07-28 21:15 [PATCHSET 0/2] xfs_io: small fixes to funshare command Darrick J. Wong
2021-07-28 21:16 ` [PATCH 2/2] xfs_io: clean up the funshare command a bit Darrick J. Wong
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=20210706182856.GC11588@locust \
--to=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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