qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Liang Li <liang.z.li@intel.com>
To: quintela@redhat.com, amit.shah@redhat.com
Cc: zhang.zhanghailiang@huawei.com, Liang Li <liang.z.li@intel.com>,
	qemu-devel@nongnu.org, dgilbert@redhat.com
Subject: [Qemu-devel] [PATCH v3 0/2] Fix flaw of qemu_put_compression_data
Date: Thu, 25 Feb 2016 11:50:25 +0800	[thread overview]
Message-ID: <1456372227-10380-1-git-send-email-liang.z.li@intel.com> (raw)

The implementation of qemu_put_compression_data only consider the case
QEMUFile is writable, it can't work with a writable QEMUFile and does
not provide any measure to prevent users from using it with a writable
QEMUFile. For safety, it should be improved to avoid some issues.

ram_save_compressed_page can be refined based on the change of
qemu_put_compression_data, very small improvement, but code looks better.

Liang Li (2):
  qemu-file: Fix qemu_put_compression_data flaw
  migration: refine ram_save_compressed_page

 migration/qemu-file.c |   23 +++++++++++++++++++++--
 migration/ram.c       |   34 ++++++++++++++++++----------------
 2 files changed, 39 insertions(+), 18 deletions(-)

             reply	other threads:[~2016-02-25  3:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25  3:50 Liang Li [this message]
2016-02-25  3:50 ` [Qemu-devel] [PATCH v3 1/2] qemu-file: Fix qemu_put_compression_data flaw Liang Li
2016-02-25  3:50 ` [Qemu-devel] [PATCH v3 2/2] migration: refine ram_save_compressed_page Liang Li
2016-03-09  8:41 ` [Qemu-devel] [PATCH v3 0/2] Fix flaw of qemu_put_compression_data Li, Liang Z
2016-03-09  8:44   ` Li, Liang Z
2016-03-09 11:01   ` Amit Shah

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=1456372227-10380-1-git-send-email-liang.z.li@intel.com \
    --to=liang.z.li@intel.com \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=zhang.zhanghailiang@huawei.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 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).