linux-kernel - Re: [PATCH] USB: add USB test and measurement class driver

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: <20080829143902.GC18136@kroah.com>
Date:	Fri, 29 Aug 2008 07:39:02 -0700
From:	Greg KH <greg@...ah.com>
To:	stefan_kopp@...lent.com
Cc:	korgull@...e.nl, stern@...land.harvard.edu, oliver@...kum.org,
	linux-usb@...r.kernel.org, me@...ipebalbi.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] USB: add USB test and measurement class driver - round
	2

On Fri, Aug 29, 2008 at 12:57:54AM -0600, stefan_kopp@...lent.com wrote:
> Hi all,
> 
> I haven't been able to follow all the enhancements you did to the
> driver, but I can comment on the ratioale behind the orignal driver.
> 
> The original driver used minor number 0 for "driver communication" (in
> contrast to "device communication"). The main purpose was to get a
> list of the USBTMC devices attached by doing a "cat /dev/usbtmc0"
> (which would point to minor number 0). The first device found would
> then use the next free minor number, usually 1. I believe the concept
> of "driver communication" has been removed from the driver, so a
> single minor number for a single device should be it.

cating that file was sending out a text file to userspace that needed to
be parsed, like a /proc file.  Now you can just look at all of the
devices in /sys/class/usb/usbtmc* to see all of the different devices in
the system.

> The issue with using cat on the shell level is that it uses fread
> which has the (in this case) ugly behaviour of recalling the driver's
> read method until the full number of characters requested has been
> accumulated (or until zero characters are returned, indicating the end
> of file). With USBTMC instruments, this behavour is bad because the
> retry will not just return zero characters, it will cause a timeout
> with the associated error condition in the device. So, to enable the
> use of echo/cat, I added some fread handling to the driver (which
> catches the retries). I believe this also has been removed, so I
> assume cat/fread will not work (?).

I do not know, but we do not do wierd things in the kernel just because
of broken userspace programs.  This logic should be done in userspace,
and programs should look at the return value of read() and handle it
properly.  Otherwise it is a bug.

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/