All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, qemu-stable@nongnu.org,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/3] block: Fix unaligned bdrv_aio_write_zeroes
Date: Mon, 27 Apr 2015 15:23:13 +0200	[thread overview]
Message-ID: <553E3841.9050205@redhat.com> (raw)
In-Reply-To: <1430140709-13599-1-git-send-email-famz@redhat.com>



On 27/04/2015 15:18, Fam Zheng wrote:
> An unaligned zero write causes NULL deferencing in bdrv_co_do_pwritev. That
> path is reachable from bdrv_co_write_zeroes and bdrv_aio_write_zeroes.
> 
> You can easily trigger through the former with qemu-io, as the test case added
> by 61815d6e0aa. For bdrv_aio_write_zeroes, in common cases there's always a
> format driver (which uses 512 alignment), so it would be much rarer to have
> unaligned requests (only concerning top level here, when the request goes down
> to bs->file, where for example the alignment is 4k, it would then be calling
> bdrv_co_write_zeroes because it's in a coroutine).
> 
> fc3959e4669a1c fixed bdrv_co_write_zeroes but not bdrv_aio_write_zeroes.  The
> lattern is the actually used one by device model. Revert the previous fix, do
> it in bdrv_co_do_pwritev, to cover both paths.
> 
> v4: "if (!qiov)" -> "if (!qiov && bytes >= align)". (Paolo)
> 
> v3: Fix the case where the unaligned request is contained within the first
>     block. (Paolo)
>     Also update iotests 033 to cover the code path with qemu-io.
> 
> v2: Split to three aligned pwritev.
> 
> 
> Fam Zheng (3):
>   Revert "block: Fix unaligned zero write"
>   block: Fix NULL deference for unaligned write if qiov is NULL
>   qemu-iotests: Test unaligned sub-block zero write
> 
>  block.c                    | 123 +++++++++++++++++++++++++--------------------
>  tests/qemu-iotests/033     |  13 +++++
>  tests/qemu-iotests/033.out |  30 +++++++++++
>  3 files changed, 111 insertions(+), 55 deletions(-)
> 

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

  parent reply	other threads:[~2015-04-27 13:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 13:18 [Qemu-devel] [PATCH v4 0/3] block: Fix unaligned bdrv_aio_write_zeroes Fam Zheng
2015-04-27 13:18 ` [Qemu-devel] [PATCH v4 1/3] Revert "block: Fix unaligned zero write" Fam Zheng
2015-04-27 13:18 ` [Qemu-devel] [PATCH v4 2/3] block: Fix NULL deference for unaligned write if qiov is NULL Fam Zheng
2015-04-27 13:18 ` [Qemu-devel] [PATCH v4 3/3] qemu-iotests: Test unaligned sub-block zero write Fam Zheng
2015-04-27 13:23 ` Paolo Bonzini [this message]
2015-04-27 13:55   ` [Qemu-devel] [PATCH v4 0/3] block: Fix unaligned bdrv_aio_write_zeroes Fam Zheng
2015-04-30 13:34 ` Kevin Wolf
2015-05-05  2:42   ` 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=553E3841.9050205@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.