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: <20100930115616.633caf91@lxorguk.ukuu.org.uk>
Date:	Thu, 30 Sep 2010 11:56:16 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Marc - A. Dahlhaus" <mad@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix capi devicenames

O> 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.

devices.txt is the spec.

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

Doesn't matter - changing them will cause regressions.

If people want to rename them in userspace then fine, but changing the
default names for device nodes is not something to do lightly. You'll
break stuff for people who do follow the spec.

So NAK, and that's with the devices@...ana.org keeper of the device name
mappings hat on.

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