linux-kernel - Re: Bug fix for pvrusb2 driver [was: Re: Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D

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: <Pine.LNX.4.64.0810231451080.1475@cnc.isely.net>
Date:	Thu, 23 Oct 2008 14:54:25 -0500 (CDT)
From:	Mike Isely <isely@...ly.net>
To:	Greg KH <greg@...ah.com>
cc:	Alan Stern <stern@...land.harvard.edu>,
	Justin Piszcz <jpiszcz@...idpixels.com>,
	Oliver Neukum <oliver@...kum.org>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB list <linux-usb@...r.kernel.org>,
	Mike Isely at pobox <isely@...ox.com>
Subject: Re: Bug fix for pvrusb2 driver [was: Re: Kernel 2.6.26.5 -> 2.6.27.2
 [USB REGRESSION] (USB -> D_STATE)]

On Thu, 23 Oct 2008, Greg KH wrote:

> On Thu, Oct 23, 2008 at 11:27:11AM -0500, Mike Isely wrote:
> > On Mon, 20 Oct 2008, Greg KH wrote:
> > 

   [...]

> > > 
> > > Will this patch be sent to the -stable group, to fix this regression in
> > > 2.6.27?  Or should they take Alan's fix instead?
> > > 
> > 
> > Greg:
> > 
> > I didn't directly answer your question here because I had figured it was 
> > answered in a previous post on this thread, that Mike Krufky had already 
> > explicitly asked that it be queued (and added his Reviewed-By tag), and 
> > that I figured it best not to add yet more noise to an already noisy 
> > group.
> > 
> > However now I see that this patch didn't get into 2.6.27.3.  It's a 
> > pretty important fix; without it the pvrusb2 driver is worse than 
> > useless (unless one adds initusbreset=0 as a module option).
> 
> As we were discussing this on Monday, and the review cycle for 2.6.27.3
> started last Saturday, it would have been pretty hard to get it into
> 2.6.27.3 :)
> 
> I need to see the patch in Linus's tree first, before it can go into any
> stable release.  Is it in there yet?  If so, please send me the git
> commit id and I'll queue it up for the next -stable round.
> 

OK, I understand.

As far as I know, Linus has not yet pulled the changes from Mauro (part 
of a larger set).  But that information is a few hours old.  I or Mike 
Krufky will let you know if/when one of us finds out.

Thanks for following up.

  -Mike


-- 

Mike Isely
isely @ pobox (dot) com
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
--
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/