linux-kernel - Re: [linux-usb-devel] 2.6.22-rc4-mm1

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: <20070608184739.GB14268@kroah.com>
Date:	Fri, 8 Jun 2007 11:47:39 -0700
From:	Greg KH <greg@...ah.com>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Grant Wilson <gww@...ndive.no-ip.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB development list <linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] 2.6.22-rc4-mm1

On Fri, Jun 08, 2007 at 10:06:21AM -0400, Alan Stern wrote:
> On Thu, 7 Jun 2007, Greg KH wrote:
> 
> > On Thu, Jun 07, 2007 at 10:53:29AM -0400, Alan Stern wrote:
> > > To tell you the truth, I rather think there's not much point in keeping
> > > usb-try-to-debug-bug-8561.patch around.  Anything seriously wrong that
> > > it could catch ought to have shown up long ago.  And it is now clear
> > > that bug 8561 has nothing to do with this; it is a programming error
> > > common to many of the USB serial drivers.  (Still waiting to hear back 
> > > from Paulo Pereira whether the fix to the USB Option driver works...)
> > 
> > What error in the usb-serial drivers are you speaking about?
> 
> The one addressed by usb-option-fix-usage-of-urb-status-abuse.patch.  I 
> thought it might be worthwhile to spend some time fixing all of these.
> Here's a quick summary showing the extent of the problem (note that 
> not all the usages are in error):

Ah, yeah, I cleaned up a lot of them a while ago, but they keep creaping
back.

I _really_ think we need to just get rid of that field and pass the
status in the urb callback.  That would fix this problem once and for
all.

But, from what I remember, the uhci host controller didn't make it easy
for me to acomplish this.  Or it might have been another host
controller, can't remember anymore...

So, anyone looking to make up some patches that touch every USB driver
in the tree?  I'd be glad to take them :)

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/