linux-kernel - Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 17 Aug 2007 10:50:23 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	"Andreas Jellinghaus [c]" <aj@...hirelabs.com>
cc:	linux-kernel@...r.kernel.org,
	<linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] why was MODALIAS removed from usb kernel
 events? [u]

On Fri, 17 Aug 2007, Andreas Jellinghaus [c] wrote:

> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9f8b17e643fe6aa505629658445849397bda4e4f
> 
> removes MODALIAS from one of the events, this breaks user space applications 
> like openct - everything that depends on getting an event that has both the
> DEVICE= path to the usb device and any information on the interface, so it
> can check if the device is something it supports (in case of openct:
> smart card reader, i.e. bInterfaceClass 0b).

There is no MODALIAS for these events because there are no drivers for 
the devices they report.  Perhaps you should be looking at 
usb_if_uevent() in drivers/usb/core/message.c instead.  Is the problem 
that this routine doesn't set DEVICE, BUSNUM, or DEVNUM?

Alan Stern

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