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]
Date:	Tue, 5 Mar 2013 14:10:50 -0800
From:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>
To:	Greg KH <gregkh@...uxfoundation.org>, stable@...r.kernel.org
Cc:	Matthias Schniedermeyer <ms@...d.de>,
	Holger Hoffstätte 
	<holger.hoffstaette@...glemail.com>,
	Jonathan Nieder <jrnieder@...il.com>,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
	Tilman Schmidt <tilman@...p.cc>, kernel-team@...ts.ubuntu.com,
	Herton Ronaldo Krzesinski <herton.krzesinski@...onical.com>
Subject: Stable backport request, Was: Re: [regression] external HDD in USB3
 enclosure cannot be dynamically removed (Re: Linux 3.7.5)

On Fri, Mar 01, 2013 at 08:48:39AM -0800, Greg KH wrote:
> On Wed, Feb 13, 2013 at 02:12:50PM -0800, Sarah Sharp wrote:
> > On Wed, Feb 13, 2013 at 01:31:29PM -0800, Greg KH wrote:
> > > On Wed, Feb 13, 2013 at 01:08:46PM -0800, Sarah Sharp wrote:
> > > > On Wed, Feb 13, 2013 at 09:04:13PM +0100, Matthias Schniedermeyer wrote:
> > > > > On 13.02.2013 11:33, Sarah Sharp wrote:
> > > > Greg,
> > > > 
> > > > How do you want to handle this?  The above four patches should go into
> > > > 3.8 and stable, but they're not currently in Linus' tree and it's
> > > > probably too late in the cycle to merge them this week.  Should we just
> > > > wait until 3.9 is out and put the patches into the stable trees then?
> > > 
> > > > My email shows that the bad commit
> > > > f7965c0846d74b270e246c1470ca955d5078eb07 has been added to the 3.2, 3.4,
> > > > and 3.7 stable trees, as well as Canonical's 3.7 stable tree.  I'm also
> > > > fine with just reverting that commit from 3.8 and stable.
> > > 
> > > It's probably easier at this point in time to just revert that commit,
> > > leave the stable kernels alone, and then everything will be fixed in
> > > 3.9.  When the commits go into Linus's tree, we can backport everything
> > > to the stable releases (including 3.8.1) at that point.
> > > 
> > > As long as someone remembers to send the needed information to
> > > stable@...r.kernel.org, I know I'll forget :)
> > > 
> > > Sound ok?
> > 
> > Yep, sounds fine.  I'll attempt to remember to send email to stable once
> > 3.9 is out.
> 
> Did this happen yet?

Nope.  Here's the upstream commit IDs of the patches that need to be
backported to stable.  Let me know if you need them in patch form:

d3b9d7a9051d7024a93c76a84b2f84b3b66ad6d5 USB: Fix connected device switch to Inactive state.
a24a6078754f28528bc91e7e7b3e6ae86bd936d8 USB: Rip out recursive call on warm port reset.
2d4fa940f99663c82ba55b2244638833b388e4e2 USB: Prepare for refactoring by adding extra udev checks.
0fe51aa5eee51db7c7ecd201d42a977ad79c58b6 USB: Don't use EHCI port sempahore for USB 3.0 hubs.

Sarah Sharp
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ