linux-kernel - Re: [PATCH 3.14 81/88] usb: hub: Prevent hub autosuspend if usbcore.autosuspend is -1

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20140904140024.GB12499@kroah.com>
Date:	Thu, 4 Sep 2014 07:00:24 -0700
From:	Greg KH <greg@...ah.com>
To:	Christoph Biedl <linux-kernel@...r.kernel.org>
Cc:	stable@...r.kernel.org
Subject: Re: [PATCH 3.14 81/88] usb: hub: Prevent hub autosuspend if
 usbcore.autosuspend is -1

On Thu, Sep 04, 2014 at 12:38:57PM +0200, Christoph Biedl wrote:
> Greg Kroah-Hartman wrote...
> 
> > 3.14-stable review patch.  If anyone has any objections, please let me know.
> 
> > From: Roger Quadros <rogerq@...com>
> > 
> > commit bdd405d2a5287bdb9b04670ea255e1f122138e66 upstream.
> 
> Obviously that one is the culprit for
> 
> drivers/usb/core/hub.c: In function 'hub_probe':
> drivers/usb/core/hub.c:1702:21: error: 'struct dev_pm_info' has no member named 'autosuspend_delay'
> make[6]: *** [drivers/usb/core/hub.o] Error 1
> make[5]: *** [drivers/usb/core] Error 2
> make[4]: *** [drivers/usb] Error 2
> 
> Also obviously usb-fix-build-error-with-config_pm_runtime-disabled.patch
> is the fix for this. My build host is still busy doing other things so
> I could not validate that yet ... but I'm pretty sure.
> 
> The problem exists in 3.16, too.

I've already queued up this patch for all branches, and should be in the
-rc2 tarball for these stable kernels.

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/