linux-kernel - Re: 2.6.28 changes in-kernel name for UVC device ?

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: <ac3eb2510901200507p4b107af6ud87a634af6679223@mail.gmail.com>
Date:	Tue, 20 Jan 2009 14:07:21 +0100
From:	Kay Sievers <kay.sievers@...y.org>
To:	Ionut Leonte <ionut.leonte@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.28 changes in-kernel name for UVC device ?

On Tue, Jan 20, 2009 at 12:49, Ionut Leonte <ionut.leonte@...il.com> wrote:
> I have a Dell laptop with an integrated webcam which works with the 'uvcvideo'
> module. For kernel versions 2.6.27 and below the following udev rule:
>
>   KERNEL=="video[0-9]*",  NAME="v4l/video%n", SYMLINK+="%k", GROUP="video"
>
> would create '/dev/video0' as a link to '/dev/v4l/video0'. When switching to
> 2.6.28 the rule creates '/dev/video1394-0' instead. Obviously most user-space
> apps were quite surprised by this (as was I).
>
> Is this change intended or is it the accidental result of some modification ?

These rules are broken, and match also on firewire devices and not
only video4linux devices.

Such rules are not part of the standard udev setup and need to be
fixed to work as intended. There is no change or fault at the kernel
side. You may just disable the firefire drivers if you don't need
them.

Btw, swapping default kernel names to devfs names and create symlinks
for the kernel names is not recommended at all.

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/