All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: kchamart@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/5] scripts: qmp-shell: allow single-quotes in JSON expressions
Date: Wed, 22 Apr 2015 10:39:44 -0400	[thread overview]
Message-ID: <5537B2B0.6080805@redhat.com> (raw)
In-Reply-To: <5537B176.9070508@redhat.com>



On 04/22/2015 10:34 AM, Eric Blake wrote:
> On 04/21/2015 08:02 PM, John Snow wrote:
>> As a convenience for the user, replace any single quotes given
>> with double quotes so that the data will deserialize correctly
>> via json.loads().
>>
>> Signed-off-by: John Snow <jsnow@redhat.com>
>> ---
>>   scripts/qmp/qmp-shell | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/scripts/qmp/qmp-shell b/scripts/qmp/qmp-shell
>> index 5347f89..d7cb33d 100755
>> --- a/scripts/qmp/qmp-shell
>> +++ b/scripts/qmp/qmp-shell
>> @@ -129,7 +129,7 @@ class QMPShell(qmp.QEMUMonitorProtocol):
>>
>>               < command-name > [ arg-name1=arg1 ] ... [ arg-nameN=argN ]
>>           """
>> -        cmdargs = cmdline.split()
>> +        cmdargs = cmdline.replace("'", '"').split()
>
> This replaces ALL single quotes, even if they would otherwise be
> escaped.  That is, if I pass foo="a\'\"b", it will probably be corrupted.
>
> qmp-shell exists mainly as a convenience for testing, and I doubt
> testers are likely to want to use unbalanced quotes as contents of
> strings, so I can give a weak:
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
> But it's still worth thinking about whether there is a more robust
> solution to be used.
>

Oh, hmm. I naively assumed that such quotes weren't permissable within 
the namespace for any valid QMP commands, but...

There's a lot of simplifying assumptions within qmp-shell already and I 
was really hoping to avoid re-architecting the parser where I just 
wanted to add a few "hit and run" improvements.

This patch could be dropped if it poses a serious problem; mostly I 
wanted to ensure that QMP commands could be entered as they are 
displayed (with single quotes!)

I'll look briefly to see if there's a quick win-button for converting 
the quotes in a "safe" way.

--js

  reply	other threads:[~2015-04-22 14:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22  2:02 [Qemu-devel] [PATCH 0/5] scripts: qmp-shell: add transaction support John Snow
2015-04-22  2:02 ` [Qemu-devel] [PATCH 1/5] scripts: qmp-shell: refactor helpers John Snow
2015-04-22 14:25   ` Eric Blake
2015-04-22  2:02 ` [Qemu-devel] [PATCH 2/5] scripts: qmp-shell: add support for [] expressions John Snow
2015-04-22 14:28   ` Eric Blake
2015-04-22 14:31     ` John Snow
2015-04-22  2:02 ` [Qemu-devel] [PATCH 3/5] scripts: qmp-shell: allow single-quotes in JSON expressions John Snow
2015-04-22 14:34   ` Eric Blake
2015-04-22 14:39     ` John Snow [this message]
2015-04-22 15:04     ` John Snow
2015-04-22 15:18       ` Eric Blake
2015-04-22  2:02 ` [Qemu-devel] [PATCH 4/5] scripts: qmp-shell: add transaction subshell John Snow
2015-04-22 14:48   ` Eric Blake
2015-04-22 15:02     ` John Snow
2015-04-22 15:28       ` Eric Blake
2015-04-22  2:02 ` [Qemu-devel] [PATCH 5/5] scripts: qmp-shell: Add verbose flag John Snow
2015-04-22 14:50   ` Eric Blake

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=5537B2B0.6080805@redhat.com \
    --to=jsnow@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kchamart@redhat.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.