From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-stable@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 2/2] block: Fix NULL deference for unaligned write if qiov is NULL
Date: Fri, 24 Apr 2015 13:00:21 +0200 [thread overview]
Message-ID: <553A2245.9060304@redhat.com> (raw)
In-Reply-To: <1429871600-10180-3-git-send-email-famz@redhat.com>
On 24/04/2015 12:33, Fam Zheng wrote:
> For zero write, qiov passed by callers (qemu-io "write -z" and
> scsi-disk "write same") is NULL.
>
> Commit fc3959e466 fixed bdrv_co_write_zeroes which is the common case
> for this bug, but it still exists in bdrv_aio_write_zeroes. A simpler
> fix would be in bdrv_co_do_pwritev which is the NULL dereference point
> and covers both cases.
>
> So don't access it in bdrv_co_do_pwritev in this case, use three aligned
> writes.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> block.c | 78 +++++++++++++++++++++++++++++++++++++++++++++++++++--------------
> 1 file changed, 61 insertions(+), 17 deletions(-)
>
> diff --git a/block.c b/block.c
> index 0fe97de..cbd0708 100644
> --- a/block.c
> +++ b/block.c
> @@ -3403,6 +3403,8 @@ static int coroutine_fn bdrv_co_do_pwritev(BlockDriverState *bs,
> */
> tracked_request_begin(&req, bs, offset, bytes, true);
>
> + assert(qiov || flags & BDRV_REQ_ZERO_WRITE);
Perhaps as a follow-up you can add
if ((flags & (BDRV_REQ_ZERO_WRITE|BDRV_REQ_MAY_UNMAP))
== BDRV_REQ_ZERO_WRITE|BDRV_REQ_MAY_UNMAP) {
qiov = NULL;
}
so that the central area is always unmapped. You can have non-NULL qiov
if the flags were added because of detect-zeroes=unmap.
But in any case that would be a separate change.
> if (offset & (align - 1)) {
> QEMUIOVector head_qiov;
> struct iovec head_iov;
> @@ -3425,13 +3427,37 @@ static int coroutine_fn bdrv_co_do_pwritev(BlockDriverState *bs,
> }
> BLKDBG_EVENT(bs, BLKDBG_PWRITEV_RMW_AFTER_HEAD);
>
> - qemu_iovec_init(&local_qiov, qiov->niov + 2);
> - qemu_iovec_add(&local_qiov, head_buf, offset & (align - 1));
> - qemu_iovec_concat(&local_qiov, qiov, 0, qiov->size);
> - use_local_qiov = true;
> + if (qiov) {
> + qemu_iovec_init(&local_qiov, qiov ? qiov->niov + 2 : 1);
> + qemu_iovec_add(&local_qiov, head_buf, offset & (align - 1));
> + qemu_iovec_concat(&local_qiov, qiov, 0, qiov->size);
> + use_local_qiov = true;
> + bytes += offset & (align - 1);
> + offset = offset & ~(align - 1);
> + } else {
> + memset(head_buf + (offset & (align - 1)), 0,
> + align - (offset & (align - 1)));
> + ret = bdrv_aligned_pwritev(bs, &req, offset & ~(align - 1), align,
> + &head_qiov, 0);
> + if (ret < 0) {
> + goto fail;
> + }
> + bytes -= align - (offset & (align - 1));
> + offset = ROUND_UP(offset, align);
> + }
> + }
>
> - bytes += offset & (align - 1);
> - offset = offset & ~(align - 1);
> + if (!qiov) {
> + uint64_t aligned_bytes = bytes & ~(align - 1);
> +
> + assert((offset & (align - 1)) == 0);
> + ret = bdrv_aligned_pwritev(bs, &req, offset, aligned_bytes,
> + NULL, flags);
> + if (ret < 0) {
> + goto fail;
> + }
> + bytes -= aligned_bytes;
> + offset += aligned_bytes;
> }
>
> if ((offset + bytes) & (align - 1)) {
> @@ -3459,21 +3485,39 @@ static int coroutine_fn bdrv_co_do_pwritev(BlockDriverState *bs,
> }
> BLKDBG_EVENT(bs, BLKDBG_PWRITEV_RMW_AFTER_TAIL);
>
> - if (!use_local_qiov) {
> - qemu_iovec_init(&local_qiov, qiov->niov + 1);
> - qemu_iovec_concat(&local_qiov, qiov, 0, qiov->size);
> - use_local_qiov = true;
> + if (qiov) {
> + if (!use_local_qiov) {
> + qemu_iovec_init(&local_qiov, qiov->niov + 1);
> + qemu_iovec_concat(&local_qiov, qiov, 0, qiov->size);
> + use_local_qiov = true;
> + }
> +
> + tail_bytes = (offset + bytes) & (align - 1);
> + qemu_iovec_add(&local_qiov, tail_buf + tail_bytes,
> + align - tail_bytes);
> +
> + bytes = ROUND_UP(bytes, align);
> + } else {
> + assert((offset & (align - 1)) == 0);
> + assert(bytes < align);
> +
> + memset(tail_buf, 0, bytes & (align - 1));
> + ret = bdrv_aligned_pwritev(bs, &req, offset, align,
> + &tail_qiov, 0);
> + if (ret < 0) {
> + goto fail;
> + }
> + offset += align;
> + bytes = 0;
> }
>
> - tail_bytes = (offset + bytes) & (align - 1);
> - qemu_iovec_add(&local_qiov, tail_buf + tail_bytes, align - tail_bytes);
> -
> - bytes = ROUND_UP(bytes, align);
> }
>
> - ret = bdrv_aligned_pwritev(bs, &req, offset, bytes,
> - use_local_qiov ? &local_qiov : qiov,
> - flags);
> + if (bytes) {
> + ret = bdrv_aligned_pwritev(bs, &req, offset, bytes,
> + use_local_qiov ? &local_qiov : qiov,
> + flags);
> + }
>
> fail:
> tracked_request_end(&req);
>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
next prev parent reply other threads:[~2015-04-24 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 10:33 [Qemu-devel] [PATCH v2 0/2] block: Fix unaligned bdrv_aio_write_zeroes Fam Zheng
2015-04-24 10:33 ` [Qemu-devel] [PATCH v2 1/2] Revert "block: Fix unaligned zero write" Fam Zheng
2015-04-24 11:12 ` Fam Zheng
2015-04-24 10:33 ` [Qemu-devel] [PATCH v2 2/2] block: Fix NULL deference for unaligned write if qiov is NULL Fam Zheng
2015-04-24 11:00 ` Paolo Bonzini [this message]
2015-04-24 11:51 ` Paolo Bonzini
2015-04-27 5:17 ` Fam Zheng
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=553A2245.9060304@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).