From: John Snow <jsnow@redhat.com>
To: Alberto Garcia <berto@igalia.com>,
Anton Nefedov <anton.nefedov@virtuozzo.com>,
Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, qemu-block@nongnu.org,
mreitz@redhat.com, Jeff Cody <jcody@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] segfault in parallel blockjobs (iotest 30)
Date: Tue, 21 Nov 2017 19:13:47 -0500 [thread overview]
Message-ID: <683910c4-1ef3-f072-caf2-87d344735d03@redhat.com> (raw)
In-Reply-To: <w51wp2jbqcd.fsf@maestria.local.igalia.com>
CC Jeff Cody
... who may or may not be preoccupied with Thanksgiving travel now.
Convenient URL for reading past replies:
https://lists.nongnu.org/archive/html/qemu-devel/2017-11/msg03844.html
On 11/21/2017 10:31 AM, Alberto Garcia wrote:
> On Tue 21 Nov 2017 04:18:13 PM CET, Anton Nefedov wrote:
>
>>>> Or, perhaps another approach, keep BlockJob referenced while it is
>>>> paused (by block_job_pause/resume_all()). That should prevent it
>>>> from deleting the BB.
>>>
>>> Yes, I tried this and it actually solves the issue. But I still think
>>> that the problem is that block jobs are allowed to finish when they
>>> are paused.
>>
>> Agree, but
>>
>>> Adding block_job_pause_point(&s->common) at the end of stream_run()
>>> fixes the problem too.
>>
>> would be a nice fix, but it only works unless the job is already
>> deferred, right?
>
> Right, I didn't mean to propose it as the proper solution (it would
> still leave mirror job vulnerable because it's already paused by the
> time it calls defer_to_main_loop()).
>
>> This:
>>
>> >> keep BlockJob referenced while it is
>> >> paused (by block_job_pause/resume_all()). That should prevent it from
>> >> deleting the BB.
>>
>> looks kind of hacky; maybe referencing in block_job_pause() (and not
>> just pause_all) seems more correct? I think it didn't work for me
>> right away though. But I can look more.
>
> You have to be careful when you unref the block job because you may
> destroy it, and therefore block_job_next() in block_job_resume_all()
> would be using freed memory.
>
> Berto
>
next prev parent reply other threads:[~2017-11-22 0:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 16:19 [Qemu-devel] segfault in parallel blockjobs (iotest 30) Anton Nefedov
2017-11-08 13:58 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-11-08 14:45 ` Alberto Garcia
2017-11-08 15:50 ` Anton Nefedov
2017-11-09 6:05 ` Fam Zheng
2017-11-09 10:03 ` Alberto Garcia
2017-11-09 16:26 ` Alberto Garcia
2017-11-10 3:02 ` Fam Zheng
2017-11-15 15:42 ` Alberto Garcia
2017-11-15 16:31 ` Anton Nefedov
2017-11-16 15:54 ` Alberto Garcia
2017-11-16 16:09 ` Anton Nefedov
2017-11-21 12:51 ` Alberto Garcia
2017-11-21 15:18 ` Anton Nefedov
2017-11-21 15:31 ` Alberto Garcia
2017-11-22 0:13 ` John Snow [this message]
2017-11-22 12:55 ` Alberto Garcia
2017-11-22 15:58 ` John Snow
2017-11-16 21:56 ` John Snow
2017-11-17 16:16 ` Alberto Garcia
2017-11-22 15:05 ` Alberto Garcia
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=683910c4-1ef3-f072-caf2-87d344735d03@redhat.com \
--to=jsnow@redhat.com \
--cc=anton.nefedov@virtuozzo.com \
--cc=berto@igalia.com \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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 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).