From: Max Reitz <mreitz@redhat.com>
To: Sergio Lopez <slp@redhat.com>, qemu-block@nongnu.org
Cc: kwolf@redhat.com, jsnow@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] blockjob: update nodes head while removing all bdrv
Date: Tue, 10 Sep 2019 15:56:42 +0200 [thread overview]
Message-ID: <aef947c6-b1df-7700-809f-4c9917abb561@redhat.com> (raw)
In-Reply-To: <20190910133611.149421-1-slp@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 2017 bytes --]
On 10.09.19 15:36, Sergio Lopez wrote:
> block_job_remove_all_bdrv() iterates through job->nodes, calling
> bdrv_root_unref_child() for each entry. The call to the latter may
> reach child_job_[can_]set_aio_ctx(), which will also attempt to
> traverse job->nodes, potentially finding entries that where freed
> on previous iterations.
>
> To avoid this situation, update job->nodes head on each iteration to
> ensure that already freed entries are no longer linked to the list.
>
> RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1746631
> Signed-off-by: Sergio Lopez <slp@redhat.com>
> ---
> Changelog
>
> v2:
> - Avoid leaking job->nodes (thanks Max Reitz)
> ---
> blockjob.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
> ---
> diff --git a/blockjob.c b/blockjob.c
> index 6e32d1a0c0..ffda6dd1e4 100644
> --- a/blockjob.c
> +++ b/blockjob.c
> @@ -187,13 +187,21 @@ static const BdrvChildRole child_job = {
>
> void block_job_remove_all_bdrv(BlockJob *job)
> {
> - GSList *l;
> + GSList *l, *orig_nodes;
> +
> + orig_nodes = job->nodes;
> for (l = job->nodes; l; l = l->next) {
> BdrvChild *c = l->data;
> bdrv_op_unblock_all(c->bs, job->blocker);
> bdrv_root_unref_child(c);
> + /*
> + * The call above may reach child_job_[can_]set_aio_ctx(), which will
> + * also traverse job->nodes, so update the head here to make sure it
> + * doesn't attempt to process an already freed BdrvChild.
> + */
> + job->nodes = l->next;
> }
> - g_slist_free(job->nodes);
> + g_slist_free(orig_nodes);
> job->nodes = NULL;
Hm, this assignment is now a no-op.
I think I’d just rewrite the whole function in the following fashion:
orig_nodes = job->nodes;
while (job->nodes) {
BdrvChild *c = job->nodes->data;
[...]
job->nodes = job->nodes->next;
}
g_slist_free(orig_nodes);
What do you think?
> }
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-09-10 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 13:36 [Qemu-devel] [PATCH v2] blockjob: update nodes head while removing all bdrv Sergio Lopez
2019-09-10 13:56 ` Max Reitz [this message]
2019-09-10 14:07 ` Sergio Lopez
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=aef947c6-b1df-7700-809f-4c9917abb561@redhat.com \
--to=mreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=slp@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).