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: <AANLkTik0DXVYgiDV0zy-m4kcsvX6X3j-8sGW4H_YT+x6@mail.gmail.com>
Date:	Thu, 30 Sep 2010 12:08:02 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	"Marc - A. Dahlhaus" <mad@....de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix capi devicenames

On Thu, Sep 30, 2010 at 11:30, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> On Wed, 29 Sep 2010 21:21:23 +0200
> "Marc - A. Dahlhaus" <mad@....de> wrote:
>
>> capi device names should get changed to what userspace expects.
>
> If userspace isn't following the spec (which has been the spec for many
> years) then thats not our problem.
>
>> Without this change recent udev versions can't produce working device
>> nodes as the capi control device node name "capi" collides with the
>> "capi" directory under which userspace expects to get the application
>> device nodes. This also fixes the Documentation.
>
> The documentation isn't broken, the documentation *is* the reference.
>
> NAK. Fix udev.
>
> We have a spec for a reason, if some distro didn't follow it then that's
> up to them but they can sort out their own udev.

There is nothing really to fix in udev, it knows nothing about ISDN.
The kernel defines the device node names these day, and udev manages
only permissions and possible symlinks.

devices.txt is just wrong in some things, and the common userspace
usage pattern is much closer to be a 'standard' here than this file.
devices.txt should catch up here. The same is true for scdX vs. srX,
scdX nodes don't exist today, and srX is not at all deprecated, unlike
devices.txt states.

The kernel provided ISDN nodes never made sense for applications using
ISDN. Also the devices.txt node names, I've never seen anywhere else
than in devices.txt.

The patch looks sane to me.

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/