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: <AANLkTi=d+5uDVK9RHguSmwFhKLVUPXvzo=G3s=NKKDW3@mail.gmail.com>
Date:	Thu, 30 Sep 2010 12:50:18 +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

On Thu, Sep 30, 2010 at 12:37, Marc - A. Dahlhaus <mad@....de> wrote:
> Am Donnerstag, den 30.09.2010, 10:30 +0100 schrieb Alan Cox:
>> 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.

>> NAK. Fix udev.
>
> I don't think udev is the right place to fix this.
>
> Udev creates symlinks and is no longer able to overwrite the name
> attribute.

Right, udev has no business here. It's the kernels responsibility since a while.

If you can't rename the kernel devices right away for some reason, you
can add naming hints to the kernel, which udev and devtmpfs will
follow, and all should work.

In any case devices.txt should be fixed, it has not much to do with
the real world.

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/