From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>,
Olaf Hering <olaf@aepfle.de>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v2] tools/hotplug: Don't ever kill xenstored
Date: Tue, 24 Feb 2015 16:44:27 +0000 [thread overview]
Message-ID: <1424796267.20146.0.camel@citrix.com> (raw)
In-Reply-To: <20150224114552.GG20083@zion.uk.xensource.com>
On Tue, 2015-02-24 at 11:45 +0000, Wei Liu wrote:
> On Tue, Feb 24, 2015 at 08:05:50AM +0000, Ross Lagerwall wrote:
> > Don't kill xenstored as part of the usual service shutdown process to
> > prevent hangs on shutdown where the kernel tries to unplug a VIF
> > after xenstored has exited.
> >
> > In an ideal case with all guests cooperating, xendomains will have shut
> > down all guests before xenstored is killed.
> >
> > However in the uncooperative case, malicious or crashed guests may still
> > be running after xendomains has exited and this should not block the
> > shutdown/reboot of dom0.
> >
> > Xenstored has no state to sync to disk, and never used to be killed in
> > the sysvinit case; observe the warning in xencommons. Our testing has
> > shown regressions caused by the change in behaviour between sysvinit and
> > systemd when it comes to killing xenstored.
> >
> > Signed-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>
>
> Acked-by: Wei Liu <wei.liu2@citrix.com>
Thanks. I added "systemd: " to the subject and applied.
prev parent reply other threads:[~2015-02-24 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 8:05 [PATCH v2] tools/hotplug: Don't ever kill xenstored Ross Lagerwall
2015-02-24 11:45 ` Wei Liu
2015-02-24 16:43 ` Ian Campbell
2015-02-24 16:44 ` Ian Campbell [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=1424796267.20146.0.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--cc=ross.lagerwall@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.