From: Max Reitz <mreitz@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>, eblake@redhat.com
Cc: kwolf@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qemu-io: Reinitialize optind to 1 (not 0) before parsing inner command.
Date: Mon, 7 Jan 2019 18:17:30 +0100 [thread overview]
Message-ID: <cb7b80d8-e54f-5422-7029-47ee286dd25f@redhat.com> (raw)
In-Reply-To: <20190103094728.31747-2-rjones@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]
On 03.01.19 10:47, Richard W.M. Jones wrote:
> On FreeBSD 11.2:
>
> $ nbdkit memory size=1M --run './qemu-io -f raw -c "aio_write 0 512" $nbd'
> Parsing error: non-numeric argument, or extraneous/unrecognized suffix -- aio_write
>
> After main option parsing, we reinitialize optind so we can parse each
> command. However reinitializing optind to 0 does not work on FreeBSD.
> What happens when you do this is optind remains 0 after the option
> parsing loop, and the result is we try to parse argv[optind] ==
> argv[0] == "aio_write" as if it was the first parameter.
>
> The FreeBSD manual page says:
>
> In order to use getopt() to evaluate multiple sets of arguments, or to
> evaluate a single set of arguments multiple times, the variable optreset
> must be set to 1 before the second and each additional set of calls to
> getopt(), and the variable optind must be reinitialized.
[...]
> Note I didn't set optreset. It's not present in glibc and the "hard
> reset" is not necessary in this context.
But it sure sounds like FreeBSD requires you to set it, doesn't it?
Max
> Signed-off-by: Richard W.M. Jones <rjones@redhat.com>
> ---
> qemu-io-cmds.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/qemu-io-cmds.c b/qemu-io-cmds.c
> index 2c39124036..aa10ed5a20 100644
> --- a/qemu-io-cmds.c
> +++ b/qemu-io-cmds.c
> @@ -114,7 +114,7 @@ static int command(BlockBackend *blk, const cmdinfo_t *ct, int argc,
> }
> }
>
> - optind = 0;
> + optind = 1;
> return ct->cfunc(blk, argc, argv);
> }
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-07 17:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 9:47 [Qemu-devel] [PATCH v2] qemu-io: Reinitialize optind to 1 (not 0) before parsing inner command Richard W.M. Jones
2019-01-03 9:47 ` Richard W.M. Jones
2019-01-03 19:46 ` Eric Blake
2019-01-07 17:17 ` Max Reitz [this message]
2019-01-07 17:46 ` Eric Blake
2019-01-07 17:50 ` Max Reitz
2019-01-07 17:59 ` Eric Blake
2019-01-07 18:14 ` Max Reitz
2019-01-07 18:45 ` Eric Blake
2019-01-09 12:30 ` Max Reitz
2019-01-07 18:40 ` Richard W.M. Jones
2019-01-08 12:16 ` Kevin Wolf
2019-01-08 14:51 ` Eric Blake
2019-01-08 15:13 ` Kevin Wolf
2019-01-08 15:35 ` Richard W.M. Jones
2019-01-09 12:33 ` Max Reitz
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=cb7b80d8-e54f-5422-7029-47ee286dd25f@redhat.com \
--to=mreitz@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.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).