linux-kernel - Re: [linux-usb-devel] [BUG] usb/core/hub.c loops forever on resume from ram due to bluetooth

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.44L0.0705030932290.3548-100000@iolanthe.rowland.org>
Date:	Thu, 3 May 2007 09:33:18 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Mark Lord <lkml@....ca>
cc:	Linux Kernel <linux-kernel@...r.kernel.org>, <marcel@...tmann.org>,
	Greg KH <gregkh@...e.de>, Andrew Morton <akpm@...l.org>,
	<linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] [BUG] usb/core/hub.c loops forever on resume
 from ram due to bluetooth

On Wed, 2 May 2007, Mark Lord wrote:

> Alan Stern wrote:
> > 
> > A better approach would be to find out why your system gets into that loop 
> > and fix the underlying cause.
> 
> Not better, just parallel.
> 
> That loop should not be unbounded, as this example proves.
> But it also shouldn't get stuck there regardless.
> 
> Two fixes needed.

If the code never gets stuck in a loop, then there's no need to check 
whether the loop is unbounded!  :-)

So only one fix needed.

Alan Stern

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