Bug 594735 - QMP: Internal JSON extension is open to clients
Summary: QMP: Internal JSON extension is open to clients
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: 7.0
Assignee: Luiz Capitulino
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 559201 580953
TreeView+ depends on / blocked
 
Reported: 2010-05-21 13:18 UTC by Luiz Capitulino
Modified: 2012-05-16 20:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-16 20:00:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Luiz Capitulino 2010-05-21 13:18:06 UTC
Description of problem:

QEMU has an internal JSON extension which allows us to write JSON code without the need of additional backslash characters.

However, this extension is available to QMP clients as well, but it shouldn't.

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.60.el6

How reproducible:


Steps to Reproduce:
1. Open a QMP connection, eg.

# qemu-kvm [...] -qmp tcp:localhost:4444,server

2. Connect via telnet and issue the following command (note the single quotes):

{ 'execute': 'qmp_capabilities' }


Actual results:

Command works.

Expected results:

An error should be returned, as this is an internal JSON extension.

Additional info:

Comment 1 RHEL Program Management 2010-05-21 13:36:07 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 2 Luiz Capitulino 2010-06-17 18:47:43 UTC
The issue here is that, we don't want clients to rely on an extension which is non-standard and could be removed later.

However, as QMP is going to be declared tech-preview, this is quite a minor issue and maybe should be fixed only in rhel6.1.

Moving to tier3.

Comment 3 RHEL Program Management 2010-07-15 14:01:23 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 5 Luiz Capitulino 2010-11-10 16:45:01 UTC
Not very important, I don't plan to fix this in 6.1.

Comment 7 Luiz Capitulino 2011-05-27 17:01:17 UTC
This doesn't have any impact on our stack, moving to RHEL7.0.

Comment 8 Luiz Capitulino 2012-05-16 20:00:32 UTC
I don't think this will be changed upstream, but in any case this is not an actual bug and it doesn't affect RHEL in any way, will just close as WONTFIX.


Note You need to log in before you can comment on or make changes to this bug.