linux-kernel - Re: [PATCH] Fix capi devicenames

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: <20100930173547.GA91193@dspnet.fr>
Date:	Thu, 30 Sep 2010 19:35:47 +0200
From:	Olivier Galibert <galibert@...ox.com>
To:	linux-kernel@...r.kernel.org, isdn@...ux-pingi.de
Subject: Re: [PATCH] Fix capi devicenames

On Thu, Sep 30, 2010 at 02:50:24PM +0200, Marc - A. Dahlhaus wrote:
[...]
> The only setup that could get broken by this is the setup that uses udev
> to handle the devices and gives the nodes different access rights or
> something.
> 
> And that already happened by the time the rules used to create the capi
> devices got removed from udev and it was right to remove them from udev
> IMO.
[...]
> capifs is already deprecated and scheduled for removal soon because udev
> is able to replace its functionality and fedora has a patch in srpm that
> removes the capifs load from capiinit.
> 
> Userspace expects the capifs device nodes.
[...]

So if I understand correctly, capifs was deprecated and is soon be
removed because udev was able to replace it given a set of rules, then
after the deprecation was done the rules were deliberately removed
from udev.  And that's supposed to be a kernel issue?

Sounds... typical, actually.

  OG.
--
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/