linux-kernel - Re: Question about dev_uevent

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: <20120925152016.GG18777@kroah.com>
Date:	Tue, 25 Sep 2012 08:20:16 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Lan Tianyu <lantianyu1986@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: Question about dev_uevent_filter

On Tue, Sep 25, 2012 at 11:13:43PM +0800, Lan Tianyu wrote:
> 
> hi Greg:

[linux-usb added as it concerns them as well]

> 	I find only devices which has bus_type or class can add uevent callback
> and output the uevent information. This is because the dev_uevent_filter just return
> true for these devices. But some device may not have class and bus_type.
> e.g usb endpoint, if we assigned them to usb_bus_type, device core will
> try to create sysfs directory link under /sys/bus/usb. But endpoint sysfs
> directory's name are same for each usb devices.e.g ep_00, every usb device will
> create the endpoint. So in this situation, we can't assign usb endpoint to
> usb_bus_type. So even if uevent callback was added and with some information,
> it still couldn't output anything. Can we add dev->type check in the
> dev_uevent_filter() and return 1 if type exits?

Wait, why do you want a uevent for a USB endpoint?  What is the problem
you are trying to solve here?

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/