From: Markus Armbruster <armbru@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: jan.kiszka@siemens.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/9] QMP: Second half of the new argument checking code
Date: Wed, 02 Jun 2010 16:41:43 +0200 [thread overview]
Message-ID: <m3typl33a0.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <20100602105428.4bf54815@redhat.com> (Luiz Capitulino's message of "Wed, 2 Jun 2010 10:54:28 -0300")
Luiz Capitulino <lcapitulino@redhat.com> writes:
> On Wed, 02 Jun 2010 09:31:24 +0200
> Markus Armbruster <armbru@redhat.com> wrote:
>
>> Luiz Capitulino <lcapitulino@redhat.com> writes:
>>
>> > This commit introduces check_client_args_type(), which is
>> > called by qmp_check_client_args() and complements the
>> > previous commit.
>> >
>> > Now the new client's argument checker code is capable of
>> > doing type checking and detecting unknown arguments.
>> >
>> > It works this way: we iterate over the client's arguments
>> > qdict and for each argument we check if it exists and if
>> > its type is correct.
>> >
>> > Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
>> > ---
>> > monitor.c | 77 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
>> > 1 files changed, 76 insertions(+), 1 deletions(-)
>> >
>> > diff --git a/monitor.c b/monitor.c
>> > index 47a0da8..14790e6 100644
>> > --- a/monitor.c
>> > +++ b/monitor.c
>> > @@ -4266,6 +4266,75 @@ typedef struct QMPArgCheckRes {
>> > } QMPArgCheckRes;
>> >
>> > /*
>> > + * Check if client's argument exists and type is correct
>> > + */
>> > +static void check_client_args_type(const char *client_arg_name,
>> > + QObject *client_arg, void *opaque)
>> > +{
>> > + QObject *obj;
>> > + QString *arg_type;
>> > + QMPArgCheckRes *res = opaque;
>> > +
>> > + if (res->result < 0) {
>> > + /* report only the first error */
>> > + return;
>> > + }
>> > +
>> > + obj = qdict_get(res->qdict, client_arg_name);
>> > + if (!obj) {
>> > + /* client arg doesn't exist */
>> > + res->result = -1;
>> > + qerror_report(QERR_INVALID_PARAMETER, client_arg_name);
>> > + return;
>> > + }
>> > +
>> > + arg_type = qobject_to_qstring(obj);
>> > + assert(arg_type != NULL);
>> > +
>> > + /* check if argument's type is correct */
>> > + switch (qstring_get_str(arg_type)[0]) {
>> > + case 'F':
>> > + case 'B':
>> > + case 's':
>> > + if (qobject_type(client_arg) != QTYPE_QSTRING) {
>> > + qerror_report(QERR_INVALID_PARAMETER_TYPE, client_arg_name,
>> > + "string");
>> > + res->result = -1;
>> > + }
>> > + break;
>> > + case 'i':
>> > + case 'l':
>> > + case 'M':
>> > + if (qobject_type(client_arg) != QTYPE_QINT) {
>> > + qerror_report(QERR_INVALID_PARAMETER_TYPE, client_arg_name, "int");
>> > + res->result = -1;
>> > + }
>> > + break;
>> > + case 'f':
>> > + case 'T':
>> > + if (qobject_type(client_arg) != QTYPE_QINT &&
>> > + qobject_type(client_arg) != QTYPE_QFLOAT) {
>> > + qerror_report(QERR_INVALID_PARAMETER_TYPE, client_arg_name,
>> > + "number");
>> > + res->result = -1;
>> > + }
>> > + break;
>> > + case 'b':
>> > + case '-':
>> > + if (qobject_type(client_arg) != QTYPE_QBOOL) {
>> > + qerror_report(QERR_INVALID_PARAMETER_TYPE, client_arg_name, "bool");
>> > + res->result = -1;
>> > + }
>> > + break;
>> > + case 'O':
>> > + /* Not checked here */
>> > + break;
>>
>> What about case '/'? I guess it doesn't make much sense for QMP, but
>> the old checker handles it. If we drop it from QMP, we should document
>> the restriction in the source.
>
> Yes, there're two args_type we don't handle in QMP because we don't have
> any of those handlers converted: '/' and '.'.
>
> I think it's unlikely to get them converted in this form, so the current
> implementation contains dead-code. I explained this in one commit log, but
> maybe it's the wrong place.
I read that commit message after I sent my comment :)
The commit message is fine; I'd like a comment in the code in addition,
not instead of the commit message.
[...]
next prev parent reply other threads:[~2010-06-02 14:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 20:41 [Qemu-devel] [PATCH 0/9]: QMP: Replace client argument checker Luiz Capitulino
2010-06-01 20:41 ` [Qemu-devel] [PATCH 1/9] QDict: Introduce qdict_get_try_bool() Luiz Capitulino
2010-06-02 6:35 ` Markus Armbruster
2010-06-02 13:53 ` Luiz Capitulino
2010-06-01 20:41 ` [Qemu-devel] [PATCH 2/9] Monitor: handle optional '-' arg as a bool Luiz Capitulino
2010-06-01 20:41 ` [Qemu-devel] [PATCH 3/9] QMP: First half of the new argument checking code Luiz Capitulino
2010-06-02 6:59 ` Markus Armbruster
2010-06-02 13:53 ` Luiz Capitulino
2010-06-03 7:35 ` Markus Armbruster
2010-06-02 7:22 ` Markus Armbruster
2010-06-02 13:53 ` Luiz Capitulino
2010-06-02 14:52 ` Markus Armbruster
2010-06-01 20:41 ` [Qemu-devel] [PATCH 4/9] QMP: Second " Luiz Capitulino
2010-06-02 7:31 ` Markus Armbruster
2010-06-02 13:54 ` Luiz Capitulino
2010-06-02 14:41 ` Markus Armbruster [this message]
2010-06-18 20:30 ` [Qemu-devel] Handling the O-type Luiz Capitulino
2010-06-21 8:12 ` Markus Armbruster
2010-06-21 15:36 ` Luiz Capitulino
2010-06-21 16:50 ` Markus Armbruster
2010-06-01 20:41 ` [Qemu-devel] [PATCH 5/9] QMP: Drop old client argument checker Luiz Capitulino
2010-06-01 20:41 ` [Qemu-devel] [PATCH 6/9] QMP: check_opts(): Minor cleanup Luiz Capitulino
2010-06-01 20:41 ` [Qemu-devel] [PATCH 7/9] QError: Introduce QERR_QMP_BAD_INPUT_OBJECT_MEMBER Luiz Capitulino
2010-06-02 7:34 ` Markus Armbruster
2010-06-01 20:41 ` [Qemu-devel] [PATCH 8/9] QMP: Introduce qmp_check_input_obj() Luiz Capitulino
2010-06-02 7:39 ` Markus Armbruster
2010-06-02 13:55 ` Luiz Capitulino
2010-06-02 14:42 ` Markus Armbruster
2010-06-01 20:41 ` [Qemu-devel] [PATCH 9/9] QMP: Drop old input object checking code Luiz Capitulino
2010-06-02 7:41 ` [Qemu-devel] [PATCH 0/9]: QMP: Replace client argument checker Markus Armbruster
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=m3typl33a0.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=lcapitulino@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.