From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
vsementsov@virtuozzo.com, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>, Jeff Cody <jcody@redhat.com>,
Eric Blake <eblake@redhat.com>, John Snow <jsnow@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 07/10] block: Use common req handling for discard
Date: Tue, 10 Jul 2018 16:45:43 +0200 [thread overview]
Message-ID: <20180710144543.GK5852@localhost.localdomain> (raw)
In-Reply-To: <20180710063124.2263-8-famz@redhat.com>
Am 10.07.2018 um 08:31 hat Fam Zheng geschrieben:
> Reuse the new bdrv_co_write_req_prepare/finish helpers. The variation
> here is that discard requests don't affect bs->wr_highest_offset, and it
> cannot extend the image.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> block/io.c | 32 ++++++++++++++++++++++----------
> 1 file changed, 22 insertions(+), 10 deletions(-)
>
> diff --git a/block/io.c b/block/io.c
> index 10a475302a..cc426bab2e 100644
> --- a/block/io.c
> +++ b/block/io.c
> @@ -1601,15 +1601,31 @@ bdrv_co_write_req_finish(BdrvChild *child, int64_t offset, uint64_t bytes,
>
> atomic_inc(&bs->write_gen);
>
> - stat64_max(&bs->wr_highest_offset, offset + bytes);
> -
> + /* Discard cannot extend the image, but in error handling cases, such as
> + * when reverting a qcow2 cluster allocation, the discarded range can pass
> + * the end of image file, so we cannot assert about BDRV_TRACKED_DISCARD
> + * here. Instead, just skip it, since semantically a discard request
> + * beyond EOF cannot expand the image anyway.
> + * */
Oh, yet another style for the end of a multiline comment. :-)
I'll fix this while applying.
Kevin
next prev parent reply other threads:[~2018-07-10 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 6:31 [Qemu-devel] [PATCH v3 00/10] block: Fix dst reading after tail copy offloading Fam Zheng
2018-07-10 6:31 ` [Qemu-devel] [PATCH v3 01/10] block: Prefix file driver trace points with "file_" Fam Zheng
2018-07-10 6:31 ` [Qemu-devel] [PATCH v3 02/10] block: Add copy offloading trace points Fam Zheng
2018-07-10 6:31 ` [Qemu-devel] [PATCH v3 03/10] block: Use BdrvChild to discard Fam Zheng
2018-07-10 6:31 ` [Qemu-devel] [PATCH v3 04/10] block: Use uint64_t for BdrvTrackedRequest byte fields Fam Zheng
2018-07-10 6:31 ` [Qemu-devel] [PATCH v3 05/10] block: Extract common write req handling Fam Zheng
2018-07-10 6:31 ` [Qemu-devel] [PATCH v3 06/10] block: Fix handling of image enlarging write Fam Zheng
2018-07-10 6:31 ` [Qemu-devel] [PATCH v3 07/10] block: Use common req handling for discard Fam Zheng
2018-07-10 14:45 ` Kevin Wolf [this message]
2018-07-10 6:31 ` [Qemu-devel] [PATCH v3 08/10] block: Use common req handling in copy offloading Fam Zheng
2018-07-10 6:31 ` [Qemu-devel] [PATCH v3 09/10] block: Fix bdrv_co_truncate overlap check Fam Zheng
2018-07-10 6:31 ` [Qemu-devel] [PATCH v3 10/10] block: Use common write req handling in truncate Fam Zheng
2018-07-10 14:46 ` [Qemu-devel] [PATCH v3 00/10] block: Fix dst reading after tail copy offloading 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=20180710144543.GK5852@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=jsnow@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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).