This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] [Xend] Move some backend configuration

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [Xend] Move some backend configuration
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Tue, 30 Sep 2008 15:58:18 +0100
Cc: Pascal Bouchareine <pascal@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 30 Sep 2008 07:59:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C507FACD.279B4%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20080930144340.GB22049@xxxxxxxxxxxxxxxxxxxxxxx> <C507FACD.279B4%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Tue, Sep 30, 2008 at 03:48:29PM +0100, Keir Fraser wrote:

> On 30/9/08 15:43, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:
> > On Tue, Sep 30, 2008 at 04:24:43PM +0200, Pascal Bouchareine wrote:
> > 
> >> This patch moves some dom0 variables and backend device
> >> configuration from frontend directories to
> >> /local/domain/<backdomid>/backend or /vm.
> > 
> > What is the point of this? These paths, however wrong they might be, are
> > API, surely.
> Which guaranteed API would that be? These paths are private to the toolstack
> implementation. Perhaps the only exception is the

Precisely the problem, there's absolutely no idea or indication what is
and isn't private. Thus you get libvirt looking in places it maybe
shouldn't, but how are they supposed to know?

I'm pretty sure this patch breaks libvirt again.

> xenconsoled-to-console-client xenstore path, but that is the one that most
> urgently needs to change, since we can't trust domUs not to mess with the
> tty path, for example.

If it's a security fix (and I see the issue), it needs to be much more
public than this patch was, and of course backported to at least 3.2


Xen-devel mailing list