Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754125AbXECNd1 (ORCPT ); Thu, 3 May 2007 09:33:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754077AbXECNd0 (ORCPT ); Thu, 3 May 2007 09:33:26 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:42583 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1754125AbXECNdZ (ORCPT ); Thu, 3 May 2007 09:33:25 -0400 Date: Thu, 3 May 2007 09:33:18 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Mark Lord cc: Linux Kernel , , Greg KH , Andrew Morton , Subject: Re: [linux-usb-devel] [BUG] usb/core/hub.c loops forever on resume from ram due to bluetooth In-Reply-To: <463904F4.8030709@rtr.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 738 Lines: 26 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/