All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Bastian Blank <waldi@debian.org>,
	Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xc: deal with xen/evtchn and xen/gntdev device names
Date: Thu, 03 Jun 2010 12:32:57 -0700	[thread overview]
Message-ID: <4C080369.3090801@goop.org> (raw)
In-Reply-To: <1275553876.24218.28795.camel@zakaz.uk.xensource.com>

On 06/03/2010 01:31 AM, Ian Campbell wrote:
> On Wed, 2010-06-02 at 17:09 +0100, Jeremy Fitzhardinge wrote:
>   
>> On 06/02/2010 02:29 AM, Ian Campbell wrote:
>>     
>>> On Tue, 2010-06-01 at 17:35 +0100, Jeremy Fitzhardinge wrote:
>>> I don't think we need a flag day. It seems like we already ship a udev
>>> rule (in tools/hotplug/Linux/xen-backend.rules) which correctly
>>> created /dev/xen/evtchn with the current kernel and which is apparently
>>> unnecessary (but harmless) with the proposed kernel change.
>>>   
>>>       
>> My main concern is that an old libxc will screw anyone with new kernel
>> and udev.
>>     
> Is it any more likely to screw them with a new kernel than with an old
> one?
>   

Yeah, because libxc's rummage around in sysfs will actually work.  If we
rename the devices to be correct, it won't find them and it just ends up
deleting the old device and either failing to create a new one, or
creating it with a bogus major/minor.

> If so I think that's an argument for propagating the removal of this
> functionality into stable trees sooner rather than later rather than
> papering over the craziness for even longer.
>   

Yep.

    J

  reply	other threads:[~2010-06-03 19:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-29  1:08 [PATCH] xc: deal with xen/evtchn and xen/gntdev device names Jeremy Fitzhardinge
2010-05-29  6:53 ` Bastian Blank
2010-06-01  7:56 ` Ian Campbell
2010-06-01  8:17   ` Bastian Blank
2010-06-01 16:35   ` Jeremy Fitzhardinge
2010-06-02  9:29     ` Ian Campbell
2010-06-02 16:09       ` Jeremy Fitzhardinge
2010-06-03  8:31         ` Ian Campbell
2010-06-03 19:32           ` Jeremy Fitzhardinge [this message]
2010-06-04  9:55             ` Ian Campbell
2010-06-04 10:01               ` Keir Fraser
2010-06-04 15:27               ` Dan Magenheimer
2010-06-04 15:31                 ` 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=4C080369.3090801@goop.org \
    --to=jeremy@goop.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=waldi@debian.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.