From: Kay Sievers <kay.sievers@vrfy.org>
To: Bastian Blank <waldi@debian.org>,
Michael Tokarev <mjt@tls.msk.ru>,
xen-devel@lists.xensource.com,
Jeremy Fitzhardinge <jeremy@goop.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix name of Xen event-channel device
Date: Fri, 28 May 2010 15:24:40 +0200 [thread overview]
Message-ID: <AANLkTinmhitag1oTssXB_ICXIriubGLNBvltS-Fuc8Cg@mail.gmail.com> (raw)
In-Reply-To: <20100527171313.GB11358@wavehammer.waldi.eu.org>
On Thu, May 27, 2010 at 19:13, Bastian Blank <waldi@debian.org> wrote:
> On Thu, May 27, 2010 at 08:50:39PM +0400, Michael Tokarev wrote:
>> Bastian Blank wrote:
>> > The Xen event-channel device is named evtchn in the kernel but always
>> > used as /dev/xen/evtchn in userspace. This patch fixes the name.
>> >
>> > Signed-off-by: Bastian Blank <waldi@debian.org>
>> >
>> > diff --git a/drivers/xen/evtchn.c b/drivers/xen/evtchn.c
>> > index 66e185c..89cd743 100644
>> > --- a/drivers/xen/evtchn.c
>> > +++ b/drivers/xen/evtchn.c
>> > @@ -471,7 +471,7 @@ static const struct file_operations evtchn_fops = {
>> >
>> > static struct miscdevice evtchn_miscdev = {
>> > .minor = MISC_DYNAMIC_MINOR,
>> > - .name = "evtchn",
>> > + .name = "xen/evtchn",
>>
>> Um. Will existing userspace - esp. udev rules - continue
>> to work after this change?
>
> The udev rules will just not longer match, as they only rename the
> device, this is no problem. However libxc _will_ break, as it lacks
> proper error check in its own device creation routine.
>
> However there are not much possibilities here: this support will go away
> and it will annoy every user for some time.
>
>> Also, how about other xen-related
>> devices which are moved to /dev/xen in that same udev rules?
>
> This is the only device currently supported by the vanilla kernel,
> everything else is in the Xen tree only.
And naming of primary device nodes is no longer udev's task. All these
rules are removed from the default udev rules. These names must all
come from the kernel these days. Udev will log errors if udev rules
specify names which are not in sync with the kernel, so they can be
fixed in the kernel or in the rules.
With devtmpfs the kernel needs to know all the names to create them on
its own. Udev only manages permissions, possibly creates additional
symlinks, runs programs, and distribute the events to userspace. Udev
no longer manages the naming of any primary device node.
Thanks,
Kay
next prev parent reply other threads:[~2010-05-28 13:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 10:51 Name of event-channel and other devices vs. udev Bastian Blank
2010-05-27 0:08 ` Jeremy Fitzhardinge
2010-05-27 7:35 ` Bastian Blank
2010-05-27 14:31 ` Bastian Blank
2010-05-27 15:02 ` [PATCH] Fix name of Xen event-channel device Bastian Blank
2010-05-27 16:26 ` [Xen-devel] " Konrad Rzeszutek Wilk
2010-05-27 16:50 ` Michael Tokarev
2010-05-27 17:13 ` Bastian Blank
2010-05-28 13:24 ` Kay Sievers [this message]
2010-05-28 13:41 ` Michael Tokarev
2010-05-28 23:20 ` Jeremy Fitzhardinge
2010-05-27 22:05 ` Name of event-channel and other devices vs. udev Jeremy Fitzhardinge
2010-05-27 22:26 ` Bastian Blank
2010-05-27 22:37 ` Jeremy Fitzhardinge
2010-05-27 22:58 ` Bastian Blank
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=AANLkTinmhitag1oTssXB_ICXIriubGLNBvltS-Fuc8Cg@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).