linux-kernel - Re: [PATCH] Fix name of Xen event-channel device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTinmhitag1oTssXB_ICXIriubGLNBvltS-Fuc8Cg@mail.gmail.com>
Date:	Fri, 28 May 2010 15:24:40 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Bastian Blank <waldi@...ian.org>, Michael Tokarev <mjt@....msk.ru>,
	xen-devel@...ts.xensource.com,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix name of Xen event-channel device

On Thu, May 27, 2010 at 19:13, Bastian Blank <waldi@...ian.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@...ian.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/