linux-kernel - Re: help finding entry point of USB data in the kernel, not drivers/usb/core/devio.c?

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: <48E1B7A9.5020207@cmu.edu>
Date:	Tue, 30 Sep 2008 01:22:49 -0400
From:	George Nychis <gnychis@....edu>
To:	Greg KH <greg@...ah.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: help finding entry point of USB data in the kernel, not	drivers/usb/core/devio.c?

Greg KH wrote:
> I suggest asking this on the linux-usb mailing list instead, it would
> reach the main Linux USB developers.

Thanks!  I was unaware of the list.  Punting there also.

> Wait, which way are you sending this data?  To or from the device?

I am looking for data from the device to the host.

> No, that entry point is for usbfs, not the individual drivers, and not
> the core.

I see, that explains things.

> Are you watching all of the different USB device endpoints?
> 

Yes, I am not filtering really.  But if this code is for usbfs, then 
this is definitely not what I am looking for.

I think what I am looking for might be in devices.c::usb_device_read() 
... poking around there now.  It calls usb_device_dump() which takes a 
user space buffer as a parameter for which it dumps data in to.

Thanks for the response!

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