linux-kernel - Re: Is anyone maintaining (or even using) usbtmc?

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: <cb0375e10908031449l2005a468v9683eb5a078cf226@mail.gmail.com>
Date:	Mon, 3 Aug 2009 17:49:09 -0400
From:	Andrew Lutomirski <luto@....edu>
To:	Greg KH <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
	gregkh@...e.de
Subject: Re: Is anyone maintaining (or even using) usbtmc?

On Mon, Aug 3, 2009 at 5:20 PM, Greg KH<greg@...ah.com> wrote:
> On Mon, Aug 03, 2009 at 05:14:56PM -0400, Andrew Lutomirski wrote:
>> Hi all-
>>
>> I'm trying to use usbtmc on an Aglient N9310A (The only TMC device I
>> have), and it sort of works, but it seems to be both extremely buggy
>> and missing a good deal of rather important functionality.  Is there
>> anyone maintaining it?
>
> Yes, me.
>
>> If the answer is yes, I can describe the bugs (logspam, spurious
>> errors, delayed messages, inability to read status, etc.) in greater
>> detail.
>
> Please do, but also please use the latest version, in 2.6.30.3, we fixed
> some bad problems in it recently.

I am.

Almost anything I do triggers this:

usbtmc 3-1:1.0: Unable to read data, error -110

The easiest way is to write something that wasn't a query and then try
to read.  Of course, the read should fail, but there's no reason it
should spam the logs.

On occasion, sending garbage to the device will cause even a
subsequent USBTMC_IOCTL_CLEAR to fail with ETIMEDOUT.  (Maybe I wanted
USBTMC_IOCTL_ABORT_BULK_IN?  That seems wrong, though, since
presumably the driver should manage pending Bulk-IN requests on its
own.)

On other occasions (usually triggered by sending a garbage command,
but, when this happens, the problem persists across several messages),
every response will be delayed.  That is, if I send a query, I get
back the previous query's answer or ETIMEDOUT if the previous command
wasn't a query.  This persists across closing and reopening the
device.

Sometimes write() fails with ETIMEDOUT.  This failure happens with no
perceivable delay and I have no idea why.

An ioctl for GET_CAPABILITIES would be nice, but is not mandatory.

Finally, I see no way to read the USB488 status byte or detect a
status interrupt.

>
>> Is anyone using usbtmc, or, more specifically, does anyone care about
>> backward compatibility?
>
> What do you want to change in the driver interface?

The main compatibility-breaking change is that I'd like to see
close/reopen go through the whole resynchronization procedure so that
the device starts in a sane state.  Currently I restore sanity by
doing a bunch of reads and ignoring ETIMEDOUT.

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