From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com, berto@igalia.com,
qemu-devel@nongnu.org, mreitz@redhat.com
Subject: [PATCH v5 1/6] qcow2: Fix dangling pointer after reopen for 'file'
Date: Tue, 6 Jul 2021 13:23:35 +0200 [thread overview]
Message-ID: <20210706112340.223334-2-kwolf@redhat.com> (raw)
In-Reply-To: <20210706112340.223334-1-kwolf@redhat.com>
Without an external data file, s->data_file is a second pointer with the
same value as bs->file. When changing bs->file to a different BdrvChild
and freeing the old BdrvChild, s->data_file must also be updated,
otherwise it points to freed memory and causes crashes.
This problem was caught by iotests case 245.
Fixes: df2b7086f169239ebad5d150efa29c9bb6d4f820
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
---
block/qcow2.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/block/qcow2.c b/block/qcow2.c
index ee4530cdbd..cb459ef6a6 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -962,6 +962,7 @@ static bool read_cache_sizes(BlockDriverState *bs, QemuOpts *opts,
}
typedef struct Qcow2ReopenState {
+ bool had_data_file;
Qcow2Cache *l2_table_cache;
Qcow2Cache *refcount_block_cache;
int l2_slice_size; /* Number of entries in a slice of the L2 table */
@@ -1932,6 +1933,8 @@ static int qcow2_reopen_prepare(BDRVReopenState *state,
r = g_new0(Qcow2ReopenState, 1);
state->opaque = r;
+ r->had_data_file = has_data_file(state->bs);
+
ret = qcow2_update_options_prepare(state->bs, r, state->options,
state->flags, errp);
if (ret < 0) {
@@ -1966,7 +1969,18 @@ fail:
static void qcow2_reopen_commit(BDRVReopenState *state)
{
+ BDRVQcow2State *s = state->bs->opaque;
+ Qcow2ReopenState *r = state->opaque;
+
qcow2_update_options_commit(state->bs, state->opaque);
+ if (!r->had_data_file && s->data_file != state->bs->file) {
+ /*
+ * If s->data_file is just a second pointer to bs->file (which is the
+ * case without an external data file), it may need to be updated.
+ */
+ s->data_file = state->bs->file;
+ assert(!has_data_file(state->bs));
+ }
g_free(state->opaque);
}
--
2.31.1
next prev parent reply other threads:[~2021-07-06 11:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 11:23 [PATCH v5 0/6] Make blockdev-reopen stable Kevin Wolf
2021-07-06 11:23 ` Kevin Wolf [this message]
2021-07-06 13:12 ` [PATCH v5 1/6] qcow2: Fix dangling pointer after reopen for 'file' Vladimir Sementsov-Ogievskiy
2021-07-06 13:43 ` Kevin Wolf
2021-07-06 11:23 ` [PATCH v5 2/6] block: Add bdrv_reopen_queue_free() Kevin Wolf
2021-07-06 13:18 ` Vladimir Sementsov-Ogievskiy
2021-07-06 11:23 ` [PATCH v5 3/6] block: Acquire AioContexts during bdrv_reopen_multiple() Kevin Wolf
2021-07-06 15:17 ` Vladimir Sementsov-Ogievskiy
2021-07-06 11:23 ` [PATCH v5 4/6] block: Support multiple reopening with x-blockdev-reopen Kevin Wolf
2021-07-06 15:45 ` Vladimir Sementsov-Ogievskiy
2021-07-06 11:23 ` [PATCH v5 5/6] iotests: Test reopening multiple devices at the same time Kevin Wolf
2021-07-06 15:50 ` Vladimir Sementsov-Ogievskiy
2021-07-06 11:23 ` [PATCH v5 6/6] block: Make blockdev-reopen stable API Kevin Wolf
2021-07-06 15:51 ` Vladimir Sementsov-Ogievskiy
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=20210706112340.223334-2-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=berto@igalia.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).