linux-kernel - Re: Bug with USB proc

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: <200607181004.55191.benjamin.cherian.kernel@gmail.com>
Date:	Tue, 18 Jul 2006 10:04:54 -0700
From:	Benjamin Cherian <benjamin.cherian.kernel@...il.com>
To:	Pete Zaitcev <zaitcev@...hat.com>
Cc:	linux-kernel@...r.kernel.org, linux-usb-devl@...ts.sf.net
Subject: Re: Bug with USB proc_bulk in 2.4 kernel

Pete,

> It's the same kind of question as, "who even uses 2.4 anymore".
We asked to same question to the user who told us about this bug :-). It 
happened after the user built his own kernel (2.4.32) for Fedora Core 1, 
which uses a much older version.
> By the way, did you consider an in-kernel driver? For me, it seems much
> safer to reimplement the whole thing that way than to monkey with devio
> again and risk more regressions.
We're currently using libusb. We don't have to time to patch and maintain a 
driver that's actually in the tree. And our customers are definitely not 
going to patch and build their own kernel either.

> Another option would be to change USBDEVFS_BULK to USBDEVFS_SUBMITURB.
> Did you look at doing that?
We did that as well. But when you try to reap an URB there is no timeout. So 
if something goes wrong you're stuck waiting for the operation to finish or 
for the user to physically unplug the device.

>Of course it's very tempting for me to off-load both
>the work and the responsibility on you.

All right then. I'll send you a patch that backports the string caching 
mechanism from 2.6 in a few days. Would you be able to test it with the 
210PU?

Thanks,

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