All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Bouchareine <pascal@gandi.net>
To: John Levon <levon@movementarian.org>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] [Xend] Move some backend configuration
Date: Tue, 30 Sep 2008 17:11:07 +0200	[thread overview]
Message-ID: <20080930151107.GA94862@bar.gandi.net> (raw)
In-Reply-To: <20080930145818.GC22049@totally.trollied.org.uk>

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
> ASAP.

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      

  parent reply	other threads:[~2008-09-30 15:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 14:24 [PATCH] [Xend] Move some backend configuration Pascal Bouchareine
2008-09-30 14:43 ` John Levon
2008-09-30 14:48   ` Keir Fraser
2008-09-30 14:58     ` John Levon
2008-09-30 15:09       ` Keir Fraser
2008-09-30 15:14         ` Ian Jackson
2008-09-30 15:30         ` Daniel P. Berrange
2008-09-30 16:09           ` Keir Fraser
2008-09-30 16:35             ` John Levon
2008-09-30 17:21               ` Pascal Bouchareine
2008-09-30 16:35             ` Daniel P. Berrange
2008-09-30 16:39               ` John Levon
2008-09-30 16:46               ` Keir Fraser
2008-09-30 17:08                 ` Daniel P. Berrange
2008-09-30 17:09               ` Pascal Bouchareine
2008-10-02  9:34             ` Ian Jackson
2008-10-02  9:49               ` Keir Fraser
2008-10-02 10:16                 ` Pascal Bouchareine
2008-10-02 10:20                   ` Keir Fraser
2008-10-02 10:21                   ` Ian Jackson
2008-10-02 10:28                     ` Keir Fraser
2008-10-02 10:31                       ` Ian Jackson
2008-10-02 13:45                 ` John Levon
2008-10-02 14:04                   ` Keir Fraser
2008-10-02 14:09                     ` Keir Fraser
2008-10-02 15:09                     ` John Levon
2008-10-02 15:25                       ` Keir Fraser
2008-10-02 17:21                         ` John Levon
2008-10-02 14:16                   ` Ian Jackson
2008-09-30 15:11       ` Pascal Bouchareine [this message]
2008-09-30 15:02     ` Keir Fraser
2008-09-30 15:06       ` John Levon

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=20080930151107.GA94862@bar.gandi.net \
    --to=pascal@gandi.net \
    --cc=keir.fraser@eu.citrix.com \
    --cc=levon@movementarian.org \
    --cc=xen-devel@lists.xensource.com \
    /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.