From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 24/24] block: Use common write req handling in truncate
Date: Tue, 10 Jul 2018 17:43:04 +0200 [thread overview]
Message-ID: <20180710154304.18304-25-kwolf@redhat.com> (raw)
In-Reply-To: <20180710154304.18304-1-kwolf@redhat.com>
From: Fam Zheng <famz@redhat.com>
Truncation is the last to convert from open coded req handling to
reusing helpers. This time the permission check in prepare has to adapt
to the new caller: it checks a different permission bit, and doesn't
trigger the before write notifier.
Also, truncation should always trigger a bs->total_sectors update and in
turn call parent resize_cb. Update the condition in finish helper, too.
It's intended to do a duplicated bs->read_only check before calling
bdrv_co_write_req_prepare() so that we can be more informative with the
error message, as bdrv_co_write_req_prepare() doesn't have Error
parameter.
Signed-off-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
---
block/io.c | 55 +++++++++++++++++++++++++++++++++++--------------------
1 file changed, 35 insertions(+), 20 deletions(-)
diff --git a/block/io.c b/block/io.c
index 77d38ca1d3..7100344c7b 100644
--- a/block/io.c
+++ b/block/io.c
@@ -1604,14 +1604,24 @@ bdrv_co_write_req_prepare(BdrvChild *child, int64_t offset, uint64_t bytes,
is_request_serialising_and_aligned(req));
assert(req->overlap_offset <= offset);
assert(offset + bytes <= req->overlap_offset + req->overlap_bytes);
+ assert(end_sector <= bs->total_sectors || child->perm & BLK_PERM_RESIZE);
- if (flags & BDRV_REQ_WRITE_UNCHANGED) {
- assert(child->perm & (BLK_PERM_WRITE_UNCHANGED | BLK_PERM_WRITE));
- } else {
- assert(child->perm & BLK_PERM_WRITE);
+ switch (req->type) {
+ case BDRV_TRACKED_WRITE:
+ case BDRV_TRACKED_DISCARD:
+ if (flags & BDRV_REQ_WRITE_UNCHANGED) {
+ assert(child->perm & (BLK_PERM_WRITE_UNCHANGED | BLK_PERM_WRITE));
+ } else {
+ assert(child->perm & BLK_PERM_WRITE);
+ }
+ return notifier_with_return_list_notify(&bs->before_write_notifiers,
+ req);
+ case BDRV_TRACKED_TRUNCATE:
+ assert(child->perm & BLK_PERM_RESIZE);
+ return 0;
+ default:
+ abort();
}
- assert(end_sector <= bs->total_sectors || child->perm & BLK_PERM_RESIZE);
- return notifier_with_return_list_notify(&bs->before_write_notifiers, req);
}
static inline void coroutine_fn
@@ -1631,8 +1641,9 @@ bdrv_co_write_req_finish(BdrvChild *child, int64_t offset, uint64_t bytes,
* beyond EOF cannot expand the image anyway.
*/
if (ret == 0 &&
- end_sector > bs->total_sectors &&
- req->type != BDRV_TRACKED_DISCARD) {
+ (req->type == BDRV_TRACKED_TRUNCATE ||
+ end_sector > bs->total_sectors) &&
+ req->type != BDRV_TRACKED_DISCARD) {
bs->total_sectors = end_sector;
bdrv_parent_cb_resize(bs);
bdrv_dirty_bitmap_truncate(bs, end_sector << BDRV_SECTOR_BITS);
@@ -3111,7 +3122,6 @@ int coroutine_fn bdrv_co_truncate(BdrvChild *child, int64_t offset,
int64_t old_size, new_bytes;
int ret;
- assert(child->perm & BLK_PERM_RESIZE);
/* if bs->drv == NULL, bs is closed, so there's nothing to do here */
if (!drv) {
@@ -3144,7 +3154,18 @@ int coroutine_fn bdrv_co_truncate(BdrvChild *child, int64_t offset,
* concurrently or they might be overwritten by preallocation. */
if (new_bytes) {
mark_request_serialising(&req, 1);
- wait_serialising_requests(&req);
+ }
+ if (bs->read_only) {
+ error_setg(errp, "Image is read-only");
+ ret = -EACCES;
+ goto out;
+ }
+ ret = bdrv_co_write_req_prepare(child, offset - new_bytes, new_bytes, &req,
+ 0);
+ if (ret < 0) {
+ error_setg_errno(errp, -ret,
+ "Failed to prepare request for truncation");
+ goto out;
}
if (!drv->bdrv_co_truncate) {
@@ -3156,13 +3177,6 @@ int coroutine_fn bdrv_co_truncate(BdrvChild *child, int64_t offset,
ret = -ENOTSUP;
goto out;
}
- if (bs->read_only) {
- error_setg(errp, "Image is read-only");
- ret = -EACCES;
- goto out;
- }
-
- assert(!(bs->open_flags & BDRV_O_INACTIVE));
ret = drv->bdrv_co_truncate(bs, offset, prealloc, errp);
if (ret < 0) {
@@ -3174,9 +3188,10 @@ int coroutine_fn bdrv_co_truncate(BdrvChild *child, int64_t offset,
} else {
offset = bs->total_sectors * BDRV_SECTOR_SIZE;
}
- bdrv_dirty_bitmap_truncate(bs, offset);
- bdrv_parent_cb_resize(bs);
- atomic_inc(&bs->write_gen);
+ /* It's possible that truncation succeeded but refresh_total_sectors
+ * failed, but the latter doesn't affect how we should finish the request.
+ * Pass 0 as the last parameter so that dirty bitmaps etc. are handled. */
+ bdrv_co_write_req_finish(child, offset - new_bytes, new_bytes, &req, 0);
out:
tracked_request_end(&req);
--
2.13.6
next prev parent reply other threads:[~2018-07-10 15:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 15:42 [Qemu-devel] [PULL 00/24] Block layer patches Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 01/24] block: Poll after drain on attaching a node Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 02/24] test-bdrv-drain: Test bdrv_append() to drained node Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 03/24] block: Fix copy-on-read crash with partial final cluster Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 04/24] iotests: 222: Don't run with luks Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 05/24] block/io: fix copy_range Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 06/24] block: split flags in copy_range Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 07/24] block: add BDRV_REQ_SERIALISING flag Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 08/24] block/backup: fix fleecing scheme: use serialized writes Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 09/24] qapi/block-core.json: Add missing documentation for blklogwrites log-append option Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 10/24] block/blklogwrites: Make sure the log sector size is not too small Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 11/24] Revert "block: Remove dead deprecation warning code" Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 12/24] Revert "block: Remove deprecated -drive option serial" Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 13/24] Revert "block: Remove deprecated -drive option addr" Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 14/24] Revert "block: Remove deprecated -drive geometry options" Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 15/24] block: Prefix file driver trace points with "file_" Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 16/24] block: Add copy offloading trace points Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 17/24] block: Use BdrvChild to discard Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 18/24] block: Use uint64_t for BdrvTrackedRequest byte fields Kevin Wolf
2018-07-10 15:42 ` [Qemu-devel] [PULL 19/24] block: Extract common write req handling Kevin Wolf
2018-07-10 15:43 ` [Qemu-devel] [PULL 20/24] block: Fix handling of image enlarging write Kevin Wolf
2018-07-10 15:43 ` [Qemu-devel] [PULL 21/24] block: Use common req handling for discard Kevin Wolf
2018-07-10 15:43 ` [Qemu-devel] [PULL 22/24] block: Use common req handling in copy offloading Kevin Wolf
2018-07-10 15:43 ` [Qemu-devel] [PULL 23/24] block: Fix bdrv_co_truncate overlap check Kevin Wolf
2018-07-10 15:43 ` Kevin Wolf [this message]
2018-07-10 17:19 ` [Qemu-devel] [PULL 00/24] Block layer patches Peter Maydell
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=20180710154304.18304-25-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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.