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: John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [Xend] Move some backend configuration
From: Pascal Bouchareine <pascal@xxxxxxxxx>
Date: Tue, 30 Sep 2008 17:11:07 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 30 Sep 2008 08:11:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080930145818.GC22049@xxxxxxxxxxxxxxxxxxxxxxx>
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> <20080930145818.GC22049@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11
On Tue, Sep 30, 2008 at 03:58:18PM +0100, John Levon wrote:
> 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.

Regarding compatibility:

This might not break too much stuff as we kept the original backend
path(s) at their location. Most obvious fix for other clients is
changing the reading of the backend location from the frontend directory,
but the old behaviour still works.

However, some parts (the console tty, location) have changed and
require attention.

> 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

It might well be a security fix, even if this sounds like a moderate
issue yet.

I agree this requires a quick update, but we need to discuss it here
before publicizing ?

\o/   Pascal Bouchareine - Gandi 
 g    0170393757           15, place de la Nation - 75011 Paris      

Xen-devel mailing list