qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Zhang Haoyu <zhanghy@sangfor.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6] qcow2: Buffer L1 table in snapshot refcount update
Date: Thu, 27 Nov 2014 16:09:26 +0100	[thread overview]
Message-ID: <54773EA6.7010201@redhat.com> (raw)
In-Reply-To: <546DFB6F.3020200@redhat.com>

On 2014-11-20 at 15:32, Max Reitz wrote:
> On 2014-11-11 at 16:27, Max Reitz wrote:
>> From: Zhang Haoyu <zhanghy@sangfor.com>
>>
>> Buffer the active L1 table in qcow2_update_snapshot_refcount() in order
>> to prevent in-place conversion of the L1 table buffer in the
>> BDRVQcowState to big endian and back, which would lead to data
>> corruption if that buffer was accessed concurrently. This should not
>> happen but better being safe than sorry.
>>
>> Signed-off-by: Zhang Haoyu <zhanghy@sangfor.com>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>> v6 for "snapshot: use local variable to bdrv_pwrite_sync L1 table" (I
>> changed the commit message wording to make it more clear what this patch
>> does and why we want it).
>>
>> Changes in v6:
>> - Only copy the local buffer back into s->l1_table if we are indeed
>>    accessing the local L1 table
>> - Use qemu_vfree() instead of g_free()
>> ---
>>   block/qcow2-refcount.c | 30 ++++++++++++++----------------
>>   1 file changed, 14 insertions(+), 16 deletions(-)
>
> Ping

-(Png)²

(got it? because i² = -1, ha-ha-haa)

  reply	other threads:[~2014-11-27 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 15:27 [Qemu-devel] [PATCH v6] qcow2: Buffer L1 table in snapshot refcount update Max Reitz
2014-11-20 14:32 ` Max Reitz
2014-11-27 15:09   ` Max Reitz [this message]
2014-11-28 10:29 ` Stefan Hajnoczi

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=54773EA6.7010201@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=zhanghy@sangfor.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).