qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>, Max Reitz <mreitz@redhat.com>,
	qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, stefanha@gmail.com
Subject: Re: [Qemu-devel] [PATCH V4 2/6] qcow2: add error message in qcow2_write_snapshots()
Date: Tue, 05 Nov 2013 10:19:04 +0800	[thread overview]
Message-ID: <52785598.7060606@linux.vnet.ibm.com> (raw)
In-Reply-To: <5277F987.7080000@redhat.com>

于 2013/11/5 3:46, Eric Blake 写道:
> On 11/03/2013 06:48 PM, Wenchao Xia wrote:
>>> On 14.10.2013 23:52, Wenchao Xia wrote:
>>>> The function still returns int since qcow2_snapshot_delete() will
>>>> return the number.
>>>>
>
>
>>>> @@ -227,24 +239,40 @@ static int
>>>> qcow2_write_snapshots(BlockDriverState *bs)
>>>>
>>>>            ret = bdrv_pwrite(bs->file, offset, &h, sizeof(h));
>>>>            if (ret < 0) {
>>>> +            error_setg(errp,
>>>> +                       "Failed in write of snapshot header at %"
>>>> +                       PRIi64 " with size %" PRIu64 ": %d (%s)",
>>>> +                       offset, sizeof(h), ret, strerror(-ret));
>>>
>>> Again, on 32 bit systems, sizeof(size_t) is generally 4 and not 8 (you
>>> may want to cast sizeof(h) to int and just use %d).
>>>
>>
>>    Maybe caset as (int64_t)sizeof(h) to avoid possible incomplete value?
>
> If we have objects larger than 2G (such that sizeof(h) would require
> more than 31 bits), we have other issues to worry about.  Casting to int
> and using %d is safe enough.
>
  OK, will use %d.

  reply	other threads:[~2013-11-05  2:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 21:52 [Qemu-devel] [PATCH V4 0/6] qcow2: rollback the modification on fail in snapshot creation Wenchao Xia
2013-10-14 21:52 ` [Qemu-devel] [PATCH V4 1/6] snapshot: add parameter *errp in snapshot create Wenchao Xia
2013-11-02 12:39   ` Max Reitz
2013-11-04  1:47     ` Wenchao Xia
2013-11-04 21:32       ` Max Reitz
2013-10-14 21:52 ` [Qemu-devel] [PATCH V4 2/6] qcow2: add error message in qcow2_write_snapshots() Wenchao Xia
2013-11-02 12:52   ` Max Reitz
2013-11-04  1:48     ` Wenchao Xia
2013-11-04 19:46       ` Eric Blake
2013-11-05  2:19         ` Wenchao Xia [this message]
2013-10-14 21:52 ` [Qemu-devel] [PATCH V4 3/6] qcow2: do not free clusters when fail in header update in qcow2_write_snapshots Wenchao Xia
2013-11-02 13:04   ` Max Reitz
2013-11-02 13:56     ` Max Reitz
2013-11-04  1:51       ` Wenchao Xia
2013-10-14 21:52 ` [Qemu-devel] [PATCH V4 4/6] qcow2: cancel the modification on fail in qcow2_snapshot_create() Wenchao Xia
2013-11-02 13:11   ` Max Reitz
2013-10-14 21:52 ` [Qemu-devel] [PATCH V4 5/6] blkdebug: add debug events for snapshot Wenchao Xia
2013-11-02 13:20   ` Max Reitz
2013-10-14 21:52 ` [Qemu-devel] [PATCH V4 6/6] qemu-iotests: add test for qcow2 snapshot Wenchao Xia
2013-11-02 13:34   ` Max Reitz
2013-11-01  1:35 ` [Qemu-devel] [PATCH V4 0/6] qcow2: rollback the modification on fail in snapshot creation Wenchao Xia

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=52785598.7060606@linux.vnet.ibm.com \
    --to=xiawenc@linux.vnet.ibm.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).