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: <AANLkTimRa9VsOgSkcdrg=41pskEbMhNL4D9SXeV3dztG@mail.gmail.com>
Date:	Thu, 30 Sep 2010 21:20:29 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	"Marc - A. Dahlhaus" <mad@....de>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org,
	isdn@...ux-pingi.de
Subject: Re: [PATCH] Fix capi devicenames

n Thu, Sep 30, 2010 at 14:50, Marc - A. Dahlhaus <mad@....de> wrote:
> Am Donnerstag, den 30.09.2010, 12:29 +0100 schrieb Alan Cox:
>> > In any case devices.txt should be fixed, it has not much to do with
>> > the real world.
>>
>> If some distros chose not to follow devices.txt that is their problem.
>>
>> devices.txt is the specification, and its ABI.
>>
>> It is fixed and the kernel behaviour is to follow it. Those who didn't
>> follow it, or who didn't propose a change back when it was specified in
>> the first place have only themselves to blame.
>>
>> It isn't changing, and the ISDN code should follow the spec.
>>
>> How you sort out your userspace is a problem for those who dug holes and
>> jumped down them.
>
> Well, i doubt that any distro or hand crafted setup out there is using
> anything else than the /dev/capi20 and /dev/capi/[0-9]+ devices for capi
> interaction. Because the userspace (libcapi20 & capiinit) handle just
> this devices. (i checked debian/ubuntu, fedora rawhide and gentoo and
> all are not using other device node names...)

devices.txt is just bogus in this case and states stuff which was
never used in the real world. But you don't need to touch it. Just add
the naming hints (char *(*devnode)) to the capi class and nothing will
change, the device names in /sys and everywhere else will stay as they
are today, just devtmpfs and udev will create the right device nodes
out of the kernel supplied additional information. We did this for the
rest of the kernel the same way.

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/