qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Andreas Färber" <afaerber@suse.de>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
Date: Wed, 15 Apr 2015 07:27:15 -0400	[thread overview]
Message-ID: <20150415112715.GB2952@localhost.localdomain> (raw)
In-Reply-To: <20150414095735.GC4824@noname.redhat.com>

On Tue, Apr 14, 2015 at 11:57:35AM +0200, Kevin Wolf wrote:

[snip]

> --- a/block/vhdx.c
> +++ b/block/vhdx.c
> @@ -1285,7 +1285,7 @@ static coroutine_fn int vhdx_co_writev(BlockDriverState *bs, int64_t sector_num,
>                          iov2.iov_base = qemu_blockalign(bs, iov2.iov_len);
>                          memset(iov2.iov_base, 0, iov2.iov_len);
>                          qemu_iovec_concat_iov(&hd_qiov, &iov2, 1, 0,
> -                                              sinfo.block_offset);
> +                                              iov2.iov_len);
>                          sectors_to_write += iov2.iov_len >> BDRV_SECTOR_BITS;
>                      }
>                  }

acked-by: Jeff Cody <jcody@redhat.com>

      parent reply	other threads:[~2015-04-15 11:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11  3:41 [Qemu-devel] Failing iotests in v2.3.0-rc2 / master Andreas Färber
2015-04-11 14:33 ` Andreas Färber
2015-04-13 16:42   ` Paolo Bonzini
2015-04-13 15:29 ` John Snow
2015-04-13 17:03   ` Andreas Färber
2015-04-14  9:57 ` Kevin Wolf
2015-04-15  4:53   ` Jeff Cody
2015-04-15  9:26     ` Kevin Wolf
2015-04-15  9:34       ` Andreas Färber
2015-04-15  9:47         ` Kevin Wolf
2015-04-15  9:54           ` Andreas Färber
2015-04-15 11:27   ` Jeff Cody [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=20150415112715.GB2952@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=afaerber@suse.de \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --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).