mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vincent Legout <vincent.legout@gandi.net>
To: Jan Beulich <JBeulich@suse.com>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
	xen-devel@lists.xenproject.org,
	"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
	"Juergen Gross" <jgross@suse.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] xen-blkfront: emit KOBJ_OFFLINE uevent when detaching device
Date: Wed, 5 Jul 2017 14:37:15 +0200	[thread overview]
Message-ID: <20170705123715.exc4qyllpxatxpnj@bres.gandi.net> (raw)
In-Reply-To: <595CBCB40200007800168A16@prv-mh.provo.novell.com>

On Wed, Jul 05, 2017 at 02:17:24AM -0600, Jan Beulich wrote :
> >>> On 05.07.17 at 10:08, <vincent.legout@gandi.net> wrote:
> > Without the patch, blkif_release and xlvbd_release_gendisk are never
> > called, and no call to blk_unregister_queue is made.
> 
> But isn't that what needs to be fixed then? The device should be
> removed once its last user goes away (which would be at the time
> the umount is eventually done aiui).

You mean that block-detach should fail if the device is still mounted?
or find a way to wait until all the users are gone?

I don't say that's not what should be done, but that's not what I get.
The device is removed after a block-detach, even if still mounted. So
the system is left in an unstable state without the patch.

I also just saw the --force option of xl block-detach, but from a quick
look it seems this option was actually only in xm and never in xl.


Vincent

  reply	other threads:[~2017-07-05 12:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 11:48 Vincent Legout
2017-07-04 16:59 ` Roger Pau Monné
2017-07-05  8:08   ` Vincent Legout
2017-07-05  8:17     ` [Xen-devel] " Jan Beulich
2017-07-05 12:37       ` Vincent Legout [this message]
2017-07-05 12:53         ` Jan Beulich
2017-07-05 13:30           ` Vincent Legout
2017-07-07  8:10             ` Roger Pau Monné
2017-09-05  7:28               ` Vincent Legout
2017-09-06 10:18                 ` Juergen Gross
2017-09-06 14:57                   ` Roger Pau Monné

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=20170705123715.exc4qyllpxatxpnj@bres.gandi.net \
    --to=vincent.legout@gandi.net \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.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®