From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Lucina Subject: Re: [PATCH v3] xenconsole: Ensure exclusive access to console using locks Date: Mon, 27 Jul 2015 14:44:57 +0200 Message-ID: <20150727124457.GA644@nodbug.lucina.net> References: <21938.21666.285588.16673@mariner.uk.xensource.com> <1437751781-30700-1-git-send-email-martin@lucina.net> <21938.24923.585157.992822@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZJhm3-0004GS-D0 for xen-devel@lists.xenproject.org; Mon, 27 Jul 2015 12:44:55 +0000 Content-Disposition: inline In-Reply-To: <21938.24923.585157.992822@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: xen-devel@lists.xenproject.org, Wei Liu , Ian Campbell , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Friday, 24.07.2015 at=A017: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 > > /xenconsole.. > = > Acked-by: Ian Jackson 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? Martin