From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3451DC636CE for ; Wed, 21 Jul 2021 14:26:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1DCFD6120C for ; Wed, 21 Jul 2021 14:26:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238000AbhGUNpg (ORCPT ); Wed, 21 Jul 2021 09:45:36 -0400 Received: from netrider.rowland.org ([192.131.102.5]:40079 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S239487AbhGUNmN (ORCPT ); Wed, 21 Jul 2021 09:42:13 -0400 Received: (qmail 634121 invoked by uid 1000); 21 Jul 2021 10:22:16 -0400 Date: Wed, 21 Jul 2021 10:22:16 -0400 From: Alan Stern To: dave penkler Cc: Greg KH , qiang.zhang@windriver.com, Dmitry Vyukov , paulmck@kernel.org, Guido , USB Subject: Re: [PATCH] USB: usbtmc: Fix RCU stall warning Message-ID: <20210721142216.GA633399@rowland.harvard.edu> References: <20210629033236.7107-1-qiang.zhang@windriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Wed, Jul 21, 2021 at 11:44:23AM +0200, dave penkler wrote: > Sorry, the issue this patch is trying to fix occurs because the > current usbtmc driver resubmits the URB when it gets an EPROTO return. > The dummy usb host controller driver used in the syzbot tests keeps > returning the resubmitted URB with EPROTO causing a loop that starves > RCU. With an actual HCI driver it either recovers or returns an EPIPE. Are you sure about that? Have you ever observed a usbtmc device recovering and continuing to operate after an EPROTO error? An EPIPE error also seems rather unlikely -- particularly if the device is not plugged into a high-speed hub. Alan Stern > In either case no loop occurs. So for my part as a user and maintainer > this patch is not ok.