From: Juan Quintela <quintela@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Wei Yang <richardw.yang@linux.intel.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/2] migration/compress: compress QEMUFile is not writable
Date: Mon, 27 Jan 2020 16:32:01 +0100 [thread overview]
Message-ID: <87v9ow29vy.fsf@secure.laptop> (raw)
In-Reply-To: <20191107115910.GG2816@work-vm> (David Alan Gilbert's message of "Thu, 7 Nov 2019 11:59:10 +0000")
"Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:
> * Wei Yang (richardw.yang@linux.intel.com) wrote:
>> We open a file with empty_ops for compress QEMUFile, which means this is
>> not writable.
>
> That explanation sounds reasonable; but I'm confused by the history of
> this; the code was added by Liang Li in :
>
> b3be289 qemu-file: Fix qemu_put_compression_data flaw
>
> ( https://www.mail-archive.com/qemu-devel@nongnu.org/msg368974.html )
>
> with almost exactly the opposite argument; can we figure out why?
Comment of that patch is wrong, code agrees with this patch.
The patch that went in does:
- return 0;
+ if (!qemu_file_is_writable(f)) {
+ return -1;
+ }
+ qemu_fflush(f);
+ blen = IO_BUF_SIZE - sizeof(int32_t);
+ if (blen < compressBound(size)) {
+ return -1;
+ }
i.e. it move from return 0 to return -1 if we are not able to write, or
if we are not able to get enough space.
>> @@ -756,14 +753,7 @@ ssize_t qemu_put_compression_data(QEMUFile *f, z_stream *stream,
>> ssize_t blen = IO_BUF_SIZE - f->buf_index - sizeof(int32_t);
>>
>> if (blen < compressBound(size)) {
>> - if (!qemu_file_is_writable(f)) {
>> - return -1;
>> - }
>> - qemu_fflush(f);
>> - blen = IO_BUF_SIZE - sizeof(int32_t);
>> - if (blen < compressBound(size)) {
>> - return -1;
>> - }
>> + return -1;
>> }
This moves from trying some things to just return -1.
And patch is ok. compression file has a file with empty_os, so
qemu_fflush() will not help at all.
Reviewed-by: Juan Quintela <quintela@redhat.com>
Thanks, Juan.
next prev parent reply other threads:[~2020-01-27 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 2:39 [PATCH 0/2] migration/compress: refine the compress case Wei Yang
2019-10-12 2:39 ` [PATCH 1/2] migration/compress: compress QEMUFile is not writable Wei Yang
2019-11-07 11:59 ` Dr. David Alan Gilbert
2019-11-07 12:08 ` Wei Yang
2020-01-27 15:32 ` Juan Quintela [this message]
2019-10-12 2:39 ` [PATCH 2/2] migration/compress: disable compress if failed to setup Wei Yang
2019-11-07 12:11 ` Dr. David Alan Gilbert
2020-01-27 15:13 ` Juan Quintela
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=87v9ow29vy.fsf@secure.laptop \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richardw.yang@linux.intel.com \
/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.