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] [day] [month] [year] [list]
Message-ID: <20070517051420.GA10934@kroah.com>
Date:	Wed, 16 May 2007 22:14:20 -0700
From:	Greg KH <greg@...ah.com>
To:	art@...ltd.com
Cc:	linux-kernel@...r.kernel.org, torvalds@...l.org
Subject: Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem

On Wed, May 16, 2007 at 02:58:22PM -0500, art@...ltd.com wrote:
>  greg
> 
>  CONFIG_SYSFS_DEPRECATED=Y
> 
>  check that we have
>  rwxrwxrwx 1 root root       15 May 16 13:43 scanner-usbdev2.12 -> 
>  bus/usb/002/012
> 
>  in /dev directory after usb-scanner connection for kernel-2.6.20
>  we don't have this for kernel-2.6.22

Who creates that?  udev?  What udev rule does that?

Can you run 'udevtest' to see what is supposed to be matching here?
Odds are you have a broken rule somehow.


> 
>  ----------------------------2.6.20 usb-scanner connect
> 
>  # /usr/sbin/udevmonitor
> 
>  UEVENT[1179340996.886805] 
>  add@...vices/pci0000:00/0000:00:0b.1/usb2/2-2/2-2.2
>  UEVENT[1179340996.886864] add@...ass/usb_endpoint/usbdev2.12_ep00
>  UEVENT[1179340996.887438] 
>  add@...vices/pci0000:00/0000:00:0b.1/usb2/2-2/2-2.2/2-2.2:1.0
>  UEVENT[1179340996.887467] add@...ass/usb_endpoint/usbdev2.12_ep81
>  UEVENT[1179340996.887484] add@...ass/usb_endpoint/usbdev2.12_ep02
>  UEVENT[1179340996.887499] add@...ass/usb_endpoint/usbdev2.12_ep83
>  UEVENT[1179340996.887514] add@...ass/usb_device/usbdev2.12
>  UDEV  [1179340996.921506] 
>  add@...vices/pci0000:00/0000:00:0b.1/usb2/2-2/2-2.2
>  UDEV  [1179340996.936005] add@...ass/usb_endpoint/usbdev2.12_ep00
>  UDEV  [1179340996.960144] add@...ass/usb_endpoint/usbdev2.12_ep81
>  UDEV  [1179340996.963672] add@...ass/usb_endpoint/usbdev2.12_ep02
>  UDEV  [1179340996.967439] add@...ass/usb_endpoint/usbdev2.12_ep83
>  UDEV  [1179340997.240934] 
>  add@...vices/pci0000:00/0000:00:0b.1/usb2/2-2/2-2.2/2-2.2:1.0
>  UDEV  [1179340997.473142] add@...ass/usb_device/usbdev2.12

This last device is correct, and what your udev rule should be using to
create your symlink.

You didn't answer my, "what distro are you using" question.  Also, what
package created the udev rule that creates the above symlink?

thanks,

greg k-h

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ