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=-0.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FSL_HELO_FAKE,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,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 26437C2D0DB for ; Wed, 29 Jan 2020 18:04:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0192B206D4 for ; Wed, 29 Jan 2020 18:04:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="LowdrKlK" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727273AbgA2SEe (ORCPT ); Wed, 29 Jan 2020 13:04:34 -0500 Received: from mail-pj1-f68.google.com ([209.85.216.68]:36312 "EHLO mail-pj1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726328AbgA2SEd (ORCPT ); Wed, 29 Jan 2020 13:04:33 -0500 Received: by mail-pj1-f68.google.com with SMTP id gv17so130688pjb.1 for ; Wed, 29 Jan 2020 10:04:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=6QNebILk02STEyIe5/0fAJxmh4v1Dv7+qDAzRC1FUDQ=; b=LowdrKlK0P6qecyQGM0hzYenViTrLksQTfxjJ9ni4gKyCCIp1FahM6Ho5TjGK9OAVj 7oqM88GFtBs997v7Yh1XJCADc6MeqKnvobn1CGwvE1MPLZNH0uZswwf2Zu4yOPQi3Cdi 0e9TIPoczxRInL3Xrd1lCEWURMROuKtqa8IP4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=6QNebILk02STEyIe5/0fAJxmh4v1Dv7+qDAzRC1FUDQ=; b=mE9DgXn/HsYgOyIUwWpSdnB+I05d5q7/4y+Z5nUBHaA8hpPhXVsb34w6i6H5szwuAu xkC9v4y1eevJvlpmRr27d8RQFbQoLcLulN1+XtsfmqNNAfdnU9O4dExYLnR9hBPQLV93 7OXGuf85xB7U6/kuZqeOr3id9SbS2ndZl7AY+uadXPtzpn9iwDqwTc/qrAEURcRorKVu TpjvBG0B8emA0dw7E9k0Qrb1JiVB+0NKNiG1y/DL/4UKFSAgPRdAJoQlk6l0tYwABVXY 0umaGZAKXh4LA7OO92hdNi5eH23JRdpB2JTySalPah+zs0+zx6GuyQTlwKd5jGrYtASU cB6w== X-Gm-Message-State: APjAAAU1kXPlxIcg+piaqM5KQB6ZJb9Qya5Xgaz76x3h3goyhiXF/CXB OIZI1JT/HXJIhxj5GxdR/TmkoO6+r0k= X-Google-Smtp-Source: APXvYqxVUyW4yrpYAV6X6fDHS+gRG2rAx1gwUyY8QSDnEvQsn0QmEVreNGiM5X7rKr6GWTnyLky0ug== X-Received: by 2002:a17:902:bf41:: with SMTP id u1mr552856pls.207.1580321073273; Wed, 29 Jan 2020 10:04:33 -0800 (PST) Received: from google.com ([2620:15c:202:1:534:b7c0:a63c:460c]) by smtp.gmail.com with ESMTPSA id q6sm3385291pgt.47.2020.01.29.10.04.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 29 Jan 2020 10:04:32 -0800 (PST) Date: Wed, 29 Jan 2020 10:04:30 -0800 From: Brian Norris To: Franky Lin Cc: Guenter Roeck , Doug Anderson , Kalle Valo , Arend van Spriel , Hante Meuleman , Chi-Hsien Lin , Dan Carpenter , linux-wireless , "open list:BROADCOM BRCM80211 IEEE802.11n WIRELESS DRIVER" , brcm80211-dev-list , netdev , LKML , Matthias Kaehlcke Subject: Re: [PATCH] brcmfmac: abort and release host after error Message-ID: <20200129180428.GA99393@google.com> References: <20200128221457.12467-1-linux@roeck-us.net> <20200129000551.GA17256@roeck-us.net> 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) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Franky, [I'm very unfamiliar with this driver, but I had the same questions as Guenter, I think:] On Tue, Jan 28, 2020 at 04:57:59PM -0800, Franky Lin wrote: > On Tue, Jan 28, 2020 at 4:05 PM Guenter Roeck wrote: > > On Tue, Jan 28, 2020 at 03:14:45PM -0800, Doug Anderson wrote: > > > On Tue, Jan 28, 2020 at 2:15 PM Guenter Roeck wrote: > > > > --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c > > > > +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c > > > > @@ -1938,6 +1938,8 @@ static uint brcmf_sdio_readframes(struct brcmf_sdio *bus, uint maxframes) > > > > if (brcmf_sdio_hdparse(bus, bus->rxhdr, &rd_new, > > > > BRCMF_SDIO_FT_NORMAL)) { > > > > rd->len = 0; > > > > + brcmf_sdio_rxfail(bus, true, true); > > > > + sdio_release_host(bus->sdiodev->func1); > > > > > > I don't know much about this driver so I don't personally know if > > > "true, true" is the correct thing to pass to brcmf_sdio_rxfail(), but > > > it seems plausible. Definitely the fix to call sdio_release_host() is > > > sane. > > > > > > Thus, unless someone knows for sure that brcmf_sdio_rxfail()'s > > > parameters should be different: > > > > > Actually, looking at brcmf_sdio_hdparse() and its other callers, > > I think it may not be needed at all - other callers don't do it, and > > there already are some calls to brcmf_sdio_rxfail() in that function. > > It would be nice though to get a confirmation before I submit v2. > > I think invoking rxfail with both abort and NACK set to true is the > right thing to do here so that the pipeline can be properly purged. Thanks for looking here. I'm not sure I totally understand your answer: brcmf_sdio_hdparse() already calls brcmf_sdio_rxfail() in several error cases. Is it really OK to call it twice in a row? Brian