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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4BFEA2DF.8080006@msgid.tls.msk.ru>
Date:	Thu, 27 May 2010 20:50:39 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	Bastian Blank <waldi@...ian.org>, 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

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?  Also, how about other xen-related
devices which are moved to /dev/xen in that same udev rules?

Thanks!

/mjt
--
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/