From: Greg Kurz <groug@kaod.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block: fix QEMU crash with scsi-hd and drive_del
Date: Thu, 24 May 2018 10:32:00 +0200 [thread overview]
Message-ID: <20180524103200.600f6ed1@bahia.lan> (raw)
In-Reply-To: <20180524080553.GB20733@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On Thu, 24 May 2018 09:05:53 +0100
Stefan Hajnoczi <stefanha@redhat.com> wrote:
> On Thu, May 24, 2018 at 08:04:59AM +0200, Paolo Bonzini wrote:
> > On 23/05/2018 16:46, Greg Kurz wrote:
> > > Maybe change bdrv_root_unref_child() to ensure we don't call
> > > bdrv_close() with pending I/O requests ?
> > >
> > > void bdrv_root_unref_child(BdrvChild *child)
> > > {
> > > BlockDriverState *child_bs;
> > >
> > > child_bs = child->bs;
> > > + bdrv_drained_begin(child_bs);
> > > bdrv_detach_child(child);
> > > + bdrv_drained_end(child_bs);
> > > bdrv_unref(child_bs);
> > > }
> >
> > Maybe bdrv_detach_child should do it.
>
> Sounds good.
>
> Stefan
I guess it makes sense for bdrv_detach_child() to *break* blk->root without
leaving I/O requests behind. I'll just do that then.
Cheers,
--
Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-05-24 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 11:21 [Qemu-devel] [PATCH] block: fix QEMU crash with scsi-hd and drive_del Greg Kurz
2018-05-16 15:41 ` Greg KH
2018-05-16 16:53 ` Greg Kurz
2018-05-18 15:32 ` Stefan Hajnoczi
2018-05-23 14:46 ` Greg Kurz
2018-05-24 6:04 ` Paolo Bonzini
2018-05-24 8:05 ` Stefan Hajnoczi
2018-05-24 8:32 ` Greg Kurz [this message]
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=20180524103200.600f6ed1@bahia.lan \
--to=groug@kaod.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).