From: Paul Durrant <Paul.Durrant@citrix.com>
To: Bob Liu <bob.liu@oracle.com>, Roger Pau Monne <roger.pau@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [Xen-devel] [PATCH v3] xen-blkfront: dynamic configuration of per-vbd resources
Date: Wed, 27 Jul 2016 09:29:08 +0000 [thread overview]
Message-ID: <32978d4e198f4359bc7878d8474b3078@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <57987AF6.1050105@oracle.com>
> -----Original Message-----
[snip]
> >
> > Also, I'm not sure this is correct, if blkfront sees the "Closing" state on
> > blkback it will try to close the frontend and destroy the block device (see
> > blkfront_closing), and this should be avoided. You should call
> > blkfront_resume as soon as you see the backend move to the Closed or
> Closing
> > states, without calling blkfront_closing.
> >
>
> I didn't get how this can happen, backend state won't be changed to 'Closing'
> before blkfront_closing() is called.
> So I think current logic is fine.
>
Backends can go to closing before frontends, when the PV device is being detached.
Paul
next prev parent reply other threads:[~2016-07-27 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 3:21 Bob Liu
2016-07-27 8:07 ` Roger Pau Monné
2016-07-27 9:12 ` Bob Liu
2016-07-27 9:29 ` Paul Durrant [this message]
2016-07-27 10:09 ` Roger Pau Monné
2016-07-27 10:59 ` Roger Pau Monné
2016-07-27 11:21 ` Bob Liu
2016-07-27 14:24 ` Roger Pau Monné
2016-07-27 23:05 ` Bob Liu
2016-07-28 7:49 ` Roger Pau Monné
2016-07-28 9:31 ` [Xen-devel] " David Vrabel
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=32978d4e198f4359bc7878d8474b3078@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=bob.liu@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®