From: Yonit Halperin <yhalperi@redhat.com>
To: Christophe Fergeau <cfergeau@redhat.com>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] spice: abort on invalid streaming cmdline params
Date: Mon, 13 Aug 2012 12:00:41 +0300 [thread overview]
Message-ID: <5028C239.9030801@redhat.com> (raw)
In-Reply-To: <1344846752-3485-1-git-send-email-cfergeau@redhat.com>
Ack
On 08/13/2012 11:32 AM, Christophe Fergeau wrote:
> When parsing its command line parameters, spice aborts when it
> finds unexpected values, except for the 'streaming-video' option.
> This happens because the parsing of the parameters for this option
> is done using the 'name2enum' helper, which does not error out
> on unknown values. Using the 'parse_name' helper makes sure we
> error out in this case. Looking at git history, the use of
> 'name2enum' instead of 'parse_name' seems to have been an oversight,
> so let's change to that now.
>
> Fixes rhbz#831708
> ---
> ui/spice-core.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/ui/spice-core.c b/ui/spice-core.c
> index 4fc48f8..bb4f585 100644
> --- a/ui/spice-core.c
> +++ b/ui/spice-core.c
> @@ -344,7 +344,8 @@ static const char *stream_video_names[] = {
> [ SPICE_STREAM_VIDEO_FILTER ] = "filter",
> };
> #define parse_stream_video(_name) \
> - name2enum(_name, stream_video_names, ARRAY_SIZE(stream_video_names))
> + parse_name(_name, "stream video control", \
> + stream_video_names, ARRAY_SIZE(stream_video_names))
>
> static const char *compression_names[] = {
> [ SPICE_IMAGE_COMPRESS_OFF ] = "off",
prev parent reply other threads:[~2012-08-13 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 8:32 [Qemu-devel] [PATCH] spice: abort on invalid streaming cmdline params Christophe Fergeau
2012-08-13 9:00 ` Yonit Halperin [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=5028C239.9030801@redhat.com \
--to=yhalperi@redhat.com \
--cc=cfergeau@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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 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).