qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>,
	Justin Ossevoort <justin@quarantainenet.nl>,
	qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] qga/commands-posix: Fix bug in guest-fstrim
Date: Wed, 01 Apr 2015 18:49:55 +0200	[thread overview]
Message-ID: <551C21B3.40307@redhat.com> (raw)
In-Reply-To: <551BE582.1070409@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



On 01/04/2015 14:33, Eric Blake wrote:
> It's only a minor incompatibility, but a client that hard-codes
> itself to parsing "returns":0 (that is, expecting a json-number)
> will fail when talking to an older qemu that provided a json-object
> instead; while a client that expects a json-object always and can
> search for a "key":0 integer pair within that object that may or
> may not be present (we already document that clients MUST be
> prepared for dictionary members to be optional, but do NOT advise
> that clients must be prepared for a change between fundamental JSON
> types).  Yes, the backwards-incompatibility is a weak argument, but
> as my pending series will be requiring all new commands to
> whitelist a non-dict return, we might as well avoid making this
> another case for that whitelist.

That's true, and we might take the opportunity to return the number of
trimmed bytes separately for each filesystem.

Justin, would you like to take a shot at that, or just submit a new
version that doesn't include the change to the return value?

Thanks,

Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVHCGwAAoJEL/70l94x66DuMcH/1Sb013BWNwot+I0jhMEr7jF
WgaXQgIAVlxtrzspuE4cXF/TszCie/G1cGlF2oLP+GkJVivbAJFqJYNZcNDfE2Ti
OdfhyUCgYMhOYUG81IXIbwXlGca/RhuDW74+B+tEL9dnoissI4l5JWS+k4bWK3On
Pgu3gmIcLtQKTxUeDi93K25OAZNJJ9mLmf8CF4FAOUv3C5T4SN5tSkSEqQSB52by
zKcM4+cXg5fzYH5OLo6d2SEUqsUHoEVh75VKLb38vAYm3GuNcuVoMEnlSELc3nTo
A8Zrmc7swjZXqaZ6iRaXz7seiJ69XrfNWGqY+s0rGZoUK3z8/LwGSpDgmAY3pVQ=
=Goct
-----END PGP SIGNATURE-----

  reply	other threads:[~2015-04-01 16:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 15:14 [Qemu-devel] [PATCH] qga/commands-posix: Fix bug in guest-fstrim Justin Ossevoort
2015-03-31 16:52 ` Paolo Bonzini
2015-03-31 17:03   ` Eric Blake
2015-04-01  7:54     ` Paolo Bonzini
2015-04-01 12:33       ` Eric Blake
2015-04-01 16:49         ` Paolo Bonzini [this message]
2015-04-02  7:37           ` Justin Ossevoort
2015-03-31 17:01 ` 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=551C21B3.40307@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=eblake@redhat.com \
    --cc=justin@quarantainenet.nl \
    --cc=mdroth@linux.vnet.ibm.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).