qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block/qcow2: Use bdrv_truncate for size amend
Date: Wed, 02 Oct 2013 14:44:24 +0200	[thread overview]
Message-ID: <524C1528.5000103@redhat.com> (raw)
In-Reply-To: <20131002123204.GE12200@stefanha-thinkpad.redhat.com>

On 2013-10-02 14:32, Stefan Hajnoczi wrote:
> On Mon, Sep 09, 2013 at 12:17:41PM +0200, Max Reitz wrote:
>> When amending the size option for a qcow2 image, use bdrv_truncate
>> instead of qcow2_truncate directly, since the latter will not adjust the
>> total_sectors count in the BDS structure (whereas the former will).
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>> Depends on (follow-up to):
>>   - block/qcow2: Image file option amendment (series, v5)
>> ---
>>   block/qcow2.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/block/qcow2.c b/block/qcow2.c
>> index d29547b..259edfd 100644
>> --- a/block/qcow2.c
>> +++ b/block/qcow2.c
>> @@ -1997,7 +1997,7 @@ static int qcow2_amend_options(BlockDriverState *bs,
>>       }
>>   
>>       if (new_size) {
>> -        ret = qcow2_truncate(bs, new_size);
>> +        ret = bdrv_truncate(bs, new_size);
>>           if (ret < 0) {
>>               return ret;
>>           }
> It seems this patch was already squashed into
> 9296b3ed7050cc6e0645fbc3b0aea74406d7eeb2 ("qcow2: Implement
> bdrv_amend_options").

Yes, as Kevin stated in his reply to that series:
> Thanks, applied to the block branch with the following changes:
>
> - Updated patch 5 with
>    [PATCH] block/qcow2: Use bdrv_truncate for size amend

Max

      reply	other threads:[~2013-10-02 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09 10:17 [Qemu-devel] [PATCH] block/qcow2: Use bdrv_truncate for size amend Max Reitz
2013-10-02 12:32 ` Stefan Hajnoczi
2013-10-02 12:44   ` Max Reitz [this message]

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=524C1528.5000103@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.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).