Received: by 2002:a05:6358:45e:b0:b5:b6eb:e1f9 with SMTP id 30csp1728098rwe; Fri, 2 Sep 2022 02:50:13 -0700 (PDT) X-Google-Smtp-Source: AA6agR7WuVUoPkXvJ2NYjtj0R27EuPhE86GGNAdAu2xLivdfdJ/APqrJ4xt4vS3freiCYMjuHJWw X-Received: by 2002:a63:284:0:b0:41d:9b60:497c with SMTP id 126-20020a630284000000b0041d9b60497cmr29764633pgc.29.1662112213653; Fri, 02 Sep 2022 02:50:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662112213; cv=none; d=google.com; s=arc-20160816; b=JMPFNt0C2lCggcEsIe+w6mfYYIAiC/2qA1F9ifrMzD/YHfq575pDtCzTsK5FHPfDzj EFunezfsM3TKgk+QjJbotmz+oTXchB6jnOvUdwsCcELYdKC5bixSK4Gf0SU//NQILbCb Mr1dVaP4Jya83W4Jb1zMJxLkySQUVvgSZ1aCUeFDBNLEicpCscYCZ1dM5xU9d8+szKYY 3o6yj5qABNMi0u9c57qVOKc6NFH9Dkm8zFSix+OpIFx4C0bUXtQZDwy8OhC5rU1eXLzs GLqXuvQPjDEL0A+ISwxDVDE2/HRUvgUzzrnj8yV9K0r+GzUNA2qtb5Un+lPrU6bGpDqt Q+pA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=KHNwV5mx6gUjlOLCRF/PLTfLRK6Nfmd9+PtbuISOuEA=; b=VOIDdCI9JDIaz2ru7uipTKJhKOP9N1PA05g0n/9FRZ5yIxivlxaYQi11vZ+PVPouqb +BXNEJwDbjq0ApGDQalZQOwa5LGXCF49hnxh0s9ti1qzAyJb2I+fzLPv4PpWXGzW+6pi 0MUyIMSGpw0So8mS9ekR3/GloK8/K3l1PqQaycU519g7F3Pab5EG9F+bLANZVPKlDilm zmJi0PO90Bd7UxilWFGfl3lLBpQAUzrw9i0loL/ntZJagm5egahUlFhqD9xrFd9fIfTO NhU7baLkTkPKLJeFV8vZzao1vVgsx/1FwqG+93nB0Rd0aiaesjzJnptQkCMA1fWsl1Be j16Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=M0KeLwxz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id iw13-20020a170903044d00b00174e086c74csi1537510plb.573.2022.09.02.02.50.01; Fri, 02 Sep 2022 02:50:13 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=M0KeLwxz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236035AbiIBJ34 (ORCPT + 99 others); Fri, 2 Sep 2022 05:29:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37976 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236080AbiIBJ3W (ORCPT ); Fri, 2 Sep 2022 05:29:22 -0400 Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com [IPv6:2a00:1450:4864:20::630]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1705FCE336 for ; Fri, 2 Sep 2022 02:28:37 -0700 (PDT) Received: by mail-ej1-x630.google.com with SMTP id p16so2630349ejb.9 for ; Fri, 02 Sep 2022 02:28:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=KHNwV5mx6gUjlOLCRF/PLTfLRK6Nfmd9+PtbuISOuEA=; b=M0KeLwxzeSoLJxa8C1OND2HppYCPxKTP+rai1VGnNJLpVe5btrhUxlfQzFc4sRks9N Ft0uaS5zd772/WI6qZ+t1Dn7fM7tpxF9Kxk05ZFYWQH+y8akl7KHdRs90/MyhoihNUL1 iA5PBOvvB71OecyzpG5lIczD0+vDPUcrTWw6uaLegSu57Ky8WplwpIbCFzR+7YTPaFSW 0xhSV25GhqOo0TMfWHeE4Di+iPEXebOa3/d9C+noOAGDJX9dJtf/59GcdDEGwcmsiisT 3ffxu+EemzvN4fPjqmTyAQXI/CiOlduE6N3Sv6HiKJq3ilt4TiXyNTWG/sUD+CyOm9vT p/uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=KHNwV5mx6gUjlOLCRF/PLTfLRK6Nfmd9+PtbuISOuEA=; b=tKmCOImc4nMRvAi4Ulp11M0rQ9LENHVLa39lFJMB3TyFjK7Vh/gY0mB9Q6wnlzuGO0 8RwtHGKcRYX63faIyA2z3dQlpk52kMVcWwtIOtQaVagmZH06nUpOI8+6c1MdOZKWc1wB aD9oTzmztRIlv2Fqsm/zcSM9ObEvstT/unGC+bNWF8O7PmBgFGJ46zyanvkwOg2HdfQo wiatxgWboc8L+u4e5JbB6PHfgQDNS0cpf3jUtlvIt6YW2HZ38Zu6oGzOFbzpbsiUc8fE ALyGVaJ/MppP8OY/jSREtk8h0+sep4vNcvjgfXfNJPBSo65gNs3kuNFeIUyHiEvOK2uS c4eQ== X-Gm-Message-State: ACgBeo2p9+Sld6T4mt+ImHgBUQ6nzcinrBI4ImzLZLOGOG/gadDtr1Ge /SB+jpkbGMEtSuDeHM7UAiLc/rlmW8gn9vd0MBnwAA== X-Received: by 2002:a17:906:cc57:b0:73d:cdfd:28b4 with SMTP id mm23-20020a170906cc5700b0073dcdfd28b4mr25688033ejb.211.1662110915660; Fri, 02 Sep 2022 02:28:35 -0700 (PDT) MIME-Version: 1.0 References: <20220826075839.292615-1-raychi@google.com> In-Reply-To: From: Ray Chi Date: Fri, 2 Sep 2022 17:28:24 +0800 Message-ID: Subject: Re: [PATCH] usb: core: stop USB enumeration if too many retries To: Greg KH Cc: mathias.nyman@linux.intel.com, Alan Stern , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, Albert Wang , Badhri Jagan Sridharan , Puma Hsu Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 30, 2022 at 8:44 PM Greg KH wrote: > > On Fri, Aug 26, 2022 at 03:58:39PM +0800, Ray Chi wrote: > > If a broken accessory connected to a USB host, usbcore might > > keep doing enumeration retries and it will take a long time to > > cause system unstable. > > > > This patch provides a quirk to specific USB ports of the hub to > > stop USB enumeration if needed. > > Where does it ever allow the port to handle new devices in the future if > the device is removed and then a new one is added back? Or is the port > just now dead for forever? > I modified the patch according to Alan's suggestion, so the port will be working again after clearing the quirk with the v2 patch. > thanks, > > greg k-h Thanks, Ray