* [Qemu-devel] [PATCH] blockjob: update nodes head while removing all bdrv
@ 2019-09-10 11:07 Sergio Lopez
2019-09-10 11:42 ` Max Reitz
0 siblings, 1 reply; 3+ messages in thread
From: Sergio Lopez @ 2019-09-10 11:07 UTC (permalink / raw)
To: qemu-block; +Cc: kwolf, jsnow, qemu-devel, Sergio Lopez, mreitz
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>
---
blockjob.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/blockjob.c b/blockjob.c
index 6e32d1a0c0..7b1551d981 100644
--- a/blockjob.c
+++ b/blockjob.c
@@ -192,6 +192,12 @@ void block_job_remove_all_bdrv(BlockJob *job)
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);
job->nodes = NULL;
--
2.21.0
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] [PATCH] blockjob: update nodes head while removing all bdrv
2019-09-10 11:07 [Qemu-devel] [PATCH] blockjob: update nodes head while removing all bdrv Sergio Lopez
@ 2019-09-10 11:42 ` Max Reitz
2019-09-10 11:53 ` Sergio Lopez
0 siblings, 1 reply; 3+ messages in thread
From: Max Reitz @ 2019-09-10 11:42 UTC (permalink / raw)
To: Sergio Lopez, qemu-block; +Cc: kwolf, jsnow, qemu-devel
[-- Attachment #1.1: Type: text/plain, Size: 1415 bytes --]
On 10.09.19 13:07, 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>
> ---
> blockjob.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/blockjob.c b/blockjob.c
> index 6e32d1a0c0..7b1551d981 100644
> --- a/blockjob.c
> +++ b/blockjob.c
> @@ -192,6 +192,12 @@ void block_job_remove_all_bdrv(BlockJob *job)
> 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);
But this will leak the whole list.
Max
> job->nodes = NULL;
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] [PATCH] blockjob: update nodes head while removing all bdrv
2019-09-10 11:42 ` Max Reitz
@ 2019-09-10 11:53 ` Sergio Lopez
0 siblings, 0 replies; 3+ messages in thread
From: Sergio Lopez @ 2019-09-10 11:53 UTC (permalink / raw)
To: Max Reitz; +Cc: kwolf, jsnow, qemu-devel, qemu-block
[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]
Max Reitz <mreitz@redhat.com> writes:
> On 10.09.19 13:07, 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>
>> ---
>> blockjob.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/blockjob.c b/blockjob.c
>> index 6e32d1a0c0..7b1551d981 100644
>> --- a/blockjob.c
>> +++ b/blockjob.c
>> @@ -192,6 +192,12 @@ void block_job_remove_all_bdrv(BlockJob *job)
>> 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);
>
> But this will leak the whole list.
Ouch. This is what happens when you rush up things. I'll send a v2 ASAP.
Thanks,
Sergio.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-09-10 11:56 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-09-10 11:07 [Qemu-devel] [PATCH] blockjob: update nodes head while removing all bdrv Sergio Lopez
2019-09-10 11:42 ` Max Reitz
2019-09-10 11:53 ` Sergio Lopez
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).