From: Fam Zheng <famz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: pbonzini@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v6 2/3] block: Fix NULL deference for unaligned write if qiov is NULL
Date: Wed, 13 May 2015 13:03:01 +0800 [thread overview]
Message-ID: <20150513050237.GA22098@ad.nay.redhat.com> (raw)
In-Reply-To: <20150512115212.GD3696@noname.str.redhat.com>
On Tue, 05/12 13:52, Kevin Wolf wrote:
> Am 12.05.2015 um 08:09 hat Fam Zheng geschrieben:
> > For zero write, callers pass in NULL qiov (qemu-io "write -z" or
> > scsi-disk "write same").
> >
> > 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/io.c | 95 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 95 insertions(+)
> >
> > diff --git a/block/io.c b/block/io.c
> > index 4e5a92e..d766220 100644
> > --- a/block/io.c
> > +++ b/block/io.c
> > @@ -1174,6 +1174,97 @@ static int coroutine_fn bdrv_aligned_pwritev(BlockDriverState *bs,
> > return ret;
> > }
> >
> > +static int coroutine_fn bdrv_co_do_zero_pwritev(BlockDriverState *bs,
> > + int64_t offset,
> > + unsigned int bytes,
> > + BdrvRequestFlags flags)
> > +{
> > + BdrvTrackedRequest req;
> > + uint8_t *buf = NULL;
> > + QEMUIOVector local_qiov;
> > + struct iovec iov;
> > + uint64_t align = MAX(BDRV_SECTOR_SIZE, bs->request_alignment);
> > + unsigned int head_padding_bytes, tail_padding_bytes;
> > + int ret;
> > +
> > + head_padding_bytes = offset & (align - 1);
> > + tail_padding_bytes = align - ((offset + bytes) & (align - 1));
>
> Don't we have macros for these calculations?
No, I don't see any.
> > + tracked_request_begin(&req, bs, offset, bytes, true);
>
> Why duplicate this when it would already be the next line in
> bdrv_co_do_pwritev()?
I'll remove the duplication.
>
> > + mark_request_serialising(&req, align);
> > + wait_serialising_requests(&req);
>
> So this patch serialises all zero writes, even if they are perfectly
> aligned? Why?
>
> Actually, even for misaligned requests, I think the part in the middle
> doesn't require any serialisation, only the RMW parts do.
I'll move to branches.
Thanks,
Fam
next prev parent reply other threads:[~2015-05-13 5:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 6:09 [Qemu-devel] [PATCH v6 0/3] block: Fix unaligned bdrv_aio_write_zeroes Fam Zheng
2015-05-12 6:09 ` [Qemu-devel] [PATCH v6 1/3] Revert "block: Fix unaligned zero write" Fam Zheng
2015-05-12 11:52 ` Kevin Wolf
2015-05-12 6:09 ` [Qemu-devel] [PATCH v6 2/3] block: Fix NULL deference for unaligned write if qiov is NULL Fam Zheng
2015-05-12 11:52 ` Kevin Wolf
2015-05-13 5:03 ` Fam Zheng [this message]
2015-05-12 12:18 ` Stefan Hajnoczi
2015-05-13 5:03 ` Fam Zheng
2015-05-12 6:09 ` [Qemu-devel] [PATCH v6 3/3] qemu-iotests: Test unaligned sub-block zero write Fam Zheng
2015-05-12 11:54 ` Kevin Wolf
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=20150513050237.GA22098@ad.nay.redhat.com \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@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).