From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, Martin Lucina <martin@lucina.net>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel@lists.xenproject.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v3] xenconsole: Ensure exclusive access to console using locks
Date: Mon, 27 Jul 2015 16:14:26 +0100 [thread overview]
Message-ID: <1438010066.11600.18.camel@citrix.com> (raw)
In-Reply-To: <20150727132936.GD9031@zion.uk.xensource.com>
On Mon, 2015-07-27 at 14:29 +0100, Wei Liu wrote:
> On Mon, Jul 27, 2015 at 02:44:57PM +0200, Martin Lucina wrote:
> > On Friday, 24.07.2015 at 17:01, Ian Jackson wrote:
> > > Martin Lucina writes ("[PATCH v3] xenconsole: Ensure exclusive access
> > > to console using locks"):
> > > > If more than one instance of xenconsole is run against the same
> > > > DOMID
> > > > then each instance will only get some data. This change ensures
> > > > exclusive access to the console by obtaining an exclusive lock on
> > > > <XEN_LOCK_DIR>/xenconsole.<DOMID>.
> > >
> > > Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
> >
> > Can this also make it into the 4.6 release on the grounds of being a
> > bugfix
> > for xenconsole, or is this change too invasive?
> >
>
> I would say this is a bugfix. The locking pattern and implementation are
> well understood. The risk is minimal.
>
> Release-acked-by: Wei Liu <wei.liu2@citrix.com>
Applied, thanks.
next prev parent reply other threads:[~2015-07-27 15:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 17:08 [PATCH] xenconsole: Allow non-interactive use Martin Lucina
2015-07-23 8:48 ` Ian Campbell
2015-07-23 10:53 ` Wei Liu
2015-07-23 15:09 ` Martin Lucina
2015-07-23 15:23 ` Ian Campbell
2015-07-24 11:30 ` [PATCH v2] " Martin Lucina
2015-07-24 13:13 ` Ian Campbell
2015-07-24 11:36 ` [PATCH] " Martin Lucina
2015-07-24 11:44 ` Ian Campbell
2015-07-24 12:51 ` [PATCH] xenconsole: Ensure exclusive access to console using locks Martin Lucina
2015-07-24 13:11 ` Ian Campbell
2015-07-24 13:35 ` Ian Jackson
2015-07-24 13:40 ` Martin Lucina
2015-07-24 13:54 ` Ian Campbell
2015-07-24 13:32 ` Ian Jackson
2015-07-24 13:42 ` Martin Lucina
2015-07-24 14:47 ` [PATCH v2] " Martin Lucina
2015-07-24 15:07 ` Ian Jackson
2015-07-24 15:29 ` [PATCH v3] " Martin Lucina
2015-07-24 16:01 ` Ian Jackson
2015-07-27 12:44 ` Martin Lucina
2015-07-27 13:29 ` Wei Liu
2015-07-27 15:14 ` Ian Campbell [this message]
2015-07-24 15:12 ` [PATCH v2] " Ian Campbell
2015-07-24 13:42 ` [PATCH] " Ian Campbell
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=1438010066.11600.18.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=martin@lucina.net \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@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;
as well as URLs for NNTP newsgroup(s).