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] [day] [month] [year] [list]

Message-ID: <4C004FA3.1040004@goop.org>
Date:	Fri, 28 May 2010 16:20:03 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Bastian Blank <waldi@...ian.org>, Michael Tokarev <mjt@....msk.ru>,
	xen-devel@...ts.xensource.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix name of Xen event-channel device

On 05/27/2010 10:13 AM, Bastian Blank wrote:
> 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.
>   

Yeah, that's really annoying.  I can't change the kernel without also
having a flag day to update libxc.  I guess we could make sure all the
stable Xen branches get a libxc fix backported to them, but I wonder if
it would break other toolstacks?

> However there are not much possibilities here: this support will go away
> and it will annoy every user for some time.
>   

But if we don't make any kernel changes then libxc will muddle on even
if udev stops handling the device name properly?

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